Related
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
ronnieshane1 said:
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
Click to expand...
Click to collapse
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
that is how my luck goes, thanks for looking into my problem.
bweN diorD said:
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
Click to expand...
Click to collapse
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
I don't know if trying LG Flash Tool 2014 with a 10B KDZ would work any better than the TOT method without an IMEI.
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
there is a thread here in help somewhere on how to fix your imei. you would have to look into that, i really dont know how its done or whats possible.
I really need some help. Please please help. I have my LG G3 VS985 and it was on stock verizon firmware. I had lollipop and android 5.1.1. I rooted it using Kingroot and it was working fine. I used an app called Autorec and i tried flashing twrp using it and all it did was make my phone not turn on. It keeps vibrating and i really need your help or anyone. I'm very worried.
I have this same exact problem... anyone have a solution?
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
roirraW "edor" ehT said:
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
Click to expand...
Click to collapse
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Specter597 said:
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Click to expand...
Click to collapse
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
roirraW "edor" ehT said:
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
Click to expand...
Click to collapse
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Specter597 said:
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Click to expand...
Click to collapse
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
-VS98510b_01.kdz: -Thanks to @autoprime
-Mirror for VS98510b_01.kdz (10b): md5: d228ba692ef0c4704cba0b00fad8b8c
-VS98512b_00.kdz: -Thanks to @hokiealumnus for the AFH hosting
-Mirror for VS98512b_00.kdz (12b): md5: e8280b279d327b96689579a9eca22a3e
Click to expand...
Click to collapse
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place. 10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
What your phone came with doesn't affect things.
Even though your screen may stay blank, if you go through the motions of putting it in Download mode, then it will be in Download mode. Pull the battery first then put it in Download mode using the original USB cable that came with the phone, connected preferably to a USB 2.0 port that comes directly off of your PC motherboard - not through a USB hub. You can check it by looking in Windows' Device Manager to see if the "LGE..." device is listed under the Modem section.
The symptom you're having is common and isn't actually caused by a Bootstack, but by a lack of one, or probably more accurately, a catastrophic mix of conflicting partitions caused by, in this case, having one Bootstack on the device - probably 35B, and then restoring a backup that might've included only some of the partitions necessary for the Bootstack. TWRP backups don't back up the entire Bootstack, so you end up with some partitions from one, and other partitions from another, and they don't play well together.
JasmineROM and SkyDragon in particular play havok, so even if you dirty flashed either ROM after restoring a TWRP backup of either, if you had the 35B Bootstack flashed previously and didn't flash any Bootstack after dirty flashing either ROM, you'd have a mix of 24B and 35B partitions because even though the latest versions of both of those ROMs are based on 35B, they include part of the 24B Bootstack, but not even the whole thing at that. The reason they did that is because they couldn't figure out how to get the 35B modem working, and it wasn't until @xdabbeb packaged the proper Bootstacks we needed that it was realized that the 35B sbl1 - which those two ROMs don't include any kind of sbl1 partition - is necessary for the modem to work with it, so they included some 24B partitions because that modem worked fine with the older sbl1 which was still on the device from the last time the phone was flashed to stock unrooted.
We have a similar situation with 47A except in this case, besides needing the 47A sbl1 for the 47A modem to work, the 47A sbl1, in combination with the 12B aboot (bootloader) causes a QHSUSB_BULK 9008 mode type of brick, which requires different instructions for recovering than the normal KDZ or TOT methods, although it does use the TOT as part of the recovery, and then you flash the entire TOT method afterwards.
Sorry if this is TL;DR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
roirraW "edor" ehT said:
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place.
Click to expand...
Click to collapse
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
Click to expand...
Click to collapse
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Specter597 said:
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Click to expand...
Click to collapse
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
roirraW "edor" ehT said:
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
Click to expand...
Click to collapse
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Specter597 said:
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Click to expand...
Click to collapse
You're welcome. That's good. I'm uploading the TOT and KDZ elsewhere but looks like it'll take three or more hours to finish.
Good luck!
---------- Post added at 10:03 AM ---------- Previous post was at 09:27 AM ----------
@Specter597 I had put in a ticket to Android File Host and it appears the problem was caused by me. They told me there were illegal characters in the filename and said he'd contact the uploader, not realizing the uploader was me, so he didn't mention which characters are illegal - I asked so hopefully he'll reply soon and I don't have to experiment to find the right combination.
For what it's worth, thanks for helping me to find out there was a problem with some of my filenames on AFH. Doh me!
Edit 2: Turns out it was the comma I had put in the filename. I removed the comma from that one and the 10B KDZ and now they download fine. Sigh!
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Specter597 said:
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Click to expand...
Click to collapse
If the MD5 hash of the TOT you had downloaded is F22CD79F6C4924A0FE4429A8C4BABE9A, then it's the same as the TOT I have inside the 7-Zip archive you're currently downloading. That's the easiest and quickest way of checking to see if you have the right thing.
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
Edit 2: The Drivers' installation seem to be spotty.
Sometimes The LGE Android MTP Device install Fails
Sometimes the LGE Mobile for VZW USB Modem fails.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Specter597 said:
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Click to expand...
Click to collapse
You would only have to hold the Up volume button for at the very most 10 seconds, and that's probably extreme. If the Modem and Port sections list the LGE device now, you can be reasonably sure it's in Download mode. For TOT, change the port of the LGE device that's in the Port section (not Modem section) to 41.
I always use the latest drivers either from LG's or Verizon's website. 4.0.4 was the latest last I looked. I always reboot the PC (with the phone disconnected) after installing drivers. I don't bother updating the drivers to the latest if I already have working ones installed. With new drivers, it can take Windows up to 10 minutes to actually finish loading the drivers the first time you plug a new device into a new/different USB port. That's the way all USB devices work. In other words, if you plug the phone into port "A" in Download mode and you wait anywhere from seconds to minutes until it loads the drivers, and then unplug it and replug it into port "B", then it'll load the driver again. If you switch back to "A" it won't have to load the driver again, though.
They'll all load them from the same driver installation you did once.
Are you using the original USB cable that came with the phone? Letting the phone sit while plugged in, and not moving it around? Sometimes just rebooting the PC or trying different USB 2.0 ports help. In the end, sometimes trying a different PC helps.
Update: Success.
Successfully TOT'd back to 10b.
I decided (after installing/reinstalling the drivers 6 times) that even though it had said that some of the drivers failed to install, I would just say "F* it." Try it anyway. Despite the Windows installer saying that two elements of the DL Mode Driver package didn't install - it worked anyway. The other part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in. What a way to spend 12 hours of my life.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again, install xdabbeb's 47A or just play it safe ...
Specter597 said:
Update: Success.
Successfully TOT'd back to 10b.
I decided after installing/reinstalling the drivers 6 times, that even though it had said that some of the drivers failed to install, I would just F* it. Try it anyway. The part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again or just play it safe ...
Click to expand...
Click to collapse
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
roirraW "edor" ehT said:
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
Click to expand...
Click to collapse
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Specter597 said:
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Click to expand...
Click to collapse
Yes you can go straight to 47A from 10B, I've done it a few times before with no problems. Also you can try out xdabbeb's 2.0 which is lollipop not marshmallow. Very slimmed down, not a whole lot of grill to it, but very smooth and reliable. I keep going back and forth between the two myself.
Sent from my g3 using XDA Labs
Specter597 said:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
Click to expand...
Click to collapse
Not that I'm aware of. And either ROM is just fine as long as you flash the Bootstack after, and you should do that no matter what TWRP backup or ROM you flash.
So yesterday i was using my phone as usual and then all of sudden it turned off and rebooted. Well after it turned on i tried to turn on WiFi it would not turn on at all. I thought rebooting would help but no luck. Then apps would not open. Especially SuperSu. I reset my phone using the 47A kdz because for some reason 10b tot would not work. The wifi still wont turn on. Any Help?PLZ
That's odd however when flashing ROMs and KDZs don't help trying the TOT is a must. Several months ago I had a weird problem that stayed with me no matter what ROM or KDZ I flashed. After I flashed the 10B TOT, everything's been fine since. TOTs flash more partitions than KDZs.
When you tried the TOT method, if using the original .DLL that was provided to use with the VS985 doesn't work, try the .DLL that's extracted from the 35B KDZ. I have it on Android File Host - you can find a link to my section at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first link in my signature below to get to his thread. You shouldn't have had to use the newer .DLL as far as I'm aware since you were rooted and presumably using @xdabbeb 's 35B Bootstack, which contains downgraded partitions that allow flashing older KDZs (not just 35B and newer ones) and the TOT without the newer .DLL.
Even if neither .DLL worked before, try the new one now that you flashed the KDZ.
Also, when you flashed the KDZ, did you use the CSE or Normal option? If you didn't do CSE, then try a Factory Reset. If it's some errant user/system data that's causing the WIFI problem, then only using the CSE option or Factory Reset can help. Flashing the TOT also wipes all data. Move everything you want to keep from internal storage since that'll be wiped too.
roirraW "edor" ehT said:
That's odd however when flashing ROMs and KDZs don't help trying the TOT is a must. Several months ago I had a weird problem that stayed with me no matter what ROM or KDZ I flashed. After I flashed the 10B TOT, everything's been fine since. TOTs flash more partitions than KDZs.
When you tried the TOT method, if using the original .DLL that was provided to use with the VS985 doesn't work, try the .DLL that's extracted from the 35B KDZ. I have it on Android File Host - you can find a link to my section at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first link in my signature below to get to his thread. You shouldn't have had to use the newer .DLL as far as I'm aware since you were rooted and presumably using @xdabbeb 's 35B Bootstack, which contains downgraded partitions that allow flashing older KDZs (not just 35B and newer ones) and the TOT without the newer .DLL.
Even if neither .DLL worked before, try the new one now that you flashed the KDZ.
Also, when you flashed the KDZ, did you use the CSE or Normal option? If you didn't do CSE, then try a Factory Reset. If it's some errant user/system data that's causing the WIFI problem, then only using the CSE option or Factory Reset can help. Flashing the TOT also wipes all data. Move everything you want to keep from internal storage since that'll be wiped too.
Click to expand...
Click to collapse
well i kept on trying @LASERWOLF452's method "LG G3 downgrade to 10B, root and how to use TWRP with custom roms (update 6-5-2016)" but had no luck and on the flash tool i would either get the errors " Model information check fail" "fail to get mini os check" "fail to get complete status check"
and then it would just stay in a bootloop. And i used CSE flash
JustAnotherUser69245 said:
well i kept on trying @LASERWOLF452's method "LG G3 downgrade to 10B, root and how to use TWRP with custom roms (update 6-5-2016)" but had no luck and on the flash tool i would either get the errors " Model information check fail" "fail to get mini os check" "fail to get complete status check"
and then it would just stay in a bootloop. And i used CSE flash
Click to expand...
Click to collapse
Using the original USB cable? Try rebooting the PC? Using a USB 2.0 (not 3.0) port that comes directly off the motherboard, not through a hub? You're not actually clicking the Windows software's button to check the phone model info, right? If you are, don't do that.
Does your phone show up in Windows' Device Manager in the Modem section?
roirraW "edor" ehT said:
Using the original USB cable? Try rebooting the PC? Using a USB 2.0 (not 3.0) port that comes directly off the motherboard, not through a hub? You're not actually clicking the Windows software's button to check the phone model info, right? If you are, don't do that.
Does your phone show up in Windows' Device Manager in the Modem section?
Click to expand...
Click to collapse
it shows up like this.
http://imgur.com/SN5MEiT
was i supposed to download this dll. https://www.androidfilehost.com/?fid=24421527759885198 and then try the tot. Because if i did, it didnt work still.
JustAnotherUser69245 said:
it shows up like this.
Click to expand...
Click to collapse
Yep, that's right.
was i supposed to download this dll. and then try the tot. Because if i did, it didnt work still.
Click to expand...
Click to collapse
From stock unrooted 35B or higher, you use that .DLL with the TOT method. From earlier than 35B, or when you're on 35B and higher but rooted and using the custom Bootstacks that @xdabbeb provides, then you should be able to use the original .DLL but the newer one should work too.
Sometimes using a different PC helps. Since you didn't answer the questions I asked I assume the answer to all of them is affirmative when appropriate and negative when not. Is that correct? Since flashing the KDZ worked I would presume that however you did it should work for TOT too, just as long as like I said, you're not clicking the program button to read the phone info. That often leads to program crashes.
For the TOT method, are you changing the port of the correct device that's in the Port (not Modem) section of the Device Manager to port 41? For that matter, is it showing up under the Port section? I always forget until I'm actually doing the TOT method - KDZ uses the one in the Modem section, TOT uses the one in the Port section.
roirraW "edor" ehT said:
Yep, that's right.
From stock unrooted 35B or higher, you use that .DLL with the TOT method. From earlier than 35B, or when you're on 35B and higher but rooted and using the custom Bootstacks that @xdabbeb provides, then you should be able to use the original .DLL but the newer one should work too.
Sometimes using a different PC helps. Since you didn't answer the questions I asked I assume the answer to all of them is affirmative when appropriate and negative when not. Is that correct? Since flashing the KDZ worked I would presume that however you did it should work for TOT too, just as long as like I said, you're not clicking the program button to read the phone info. That often leads to program crashes.
For the TOT method, are you changing the port of the correct device that's in the Port (not Modem) section of the Device Manager to port 41? For that matter, is it showing up under the Port section? I always forget until I'm actually doing the TOT method - KDZ uses the one in the Modem section, TOT uses the one in the Port section.
Click to expand...
Click to collapse
i am on 47a unrooted using the KDZ method
yes thats correct and yes i do change the port number not the modem for the TOT method
I've used the KDZ method successfully to return to stock several times but now I have to do a warranty exchange and Verizon won't send the replacement phone because they claim they can see I didn't take any updates. So now I have to go back to stock but I can't use KDZ because the charging port is the flaky part so I can't connect to the PC. What if any alternate methods can I use?
On a related note, I am guessing the replacement will have most if not all of the latest updates and from what I've read I can no longer use Stump Root to root the phone. Alternatives?
gospodinwizard said:
I've used the KDZ method successfully to return to stock several times but now I have to do a warranty exchange and Verizon won't send the replacement phone because they claim they can see I didn't take any updates. So now I have to go back to stock but I can't use KDZ because the charging port is the flaky part so I can't connect to the PC. What if any alternate methods can I use?
On a related note, I am guessing the replacement will have most if not all of the latest updates and from what I've read I can no longer use Stump Root to root the phone. Alternatives?
Click to expand...
Click to collapse
Unfortunately, KDZ or TOT require the USB port. And those are the only way to return to full stock.
If you have root and TWRP now, I can make you a flashable zip that contains all the stock 47A partitions, including recovery, so once you'd boot out of custom recovery you'd be back to stock. I can't guarantee that it would say "Official" instead of "Modified" in the About menu, though. I also can't guarantee that the phone won't be bricked somehow, either. All the risk is on you.
Stump is still the way to go, you just have to downgrade to 10B using the TOT method and the .DLL that's extracted from the 35B KDZ. Both the TOT and correct .DLL are up in my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
roirraW "edor" ehT said:
If you have root and TWRP now, I can make you a flashable zip that contains all the stock 47A partitions, including recovery, so once you'd boot out of custom recovery you'd be back to stock. I can't guarantee that it would say "Official" instead of "Modified" in the About menu, though. I also can't guarantee that the phone won't be bricked somehow, either. All the risk is on you.
Stump is still the way to go, you just have to downgrade to 10B using the TOT method and the .DLL that's extracted from the 35B KDZ. Both the TOT and correct .DLL are up in my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Click to expand...
Click to collapse
The good news is I fiddled with USB enough to be able to successfully flash the 10B KDZ again. The weird news is that when I went to check for system updates, I was politely told my phone was up-to-date at 10B. Makes no sense to me and I'm not sure what to do about it. Any thoughts? The only reason I care about the updates is Verizon swore they wouldn't send out a replacement until I took updates. I.e. their complaint was that I hadn't taken any updates.
gospodinwizard said:
The good news is I fiddled with USB enough to be able to successfully flash the 10B KDZ again. The weird news is that when I went to check for system updates, I was politely told my phone was up-to-date at 10B. Makes no sense to me and I'm not sure what to do about it. Any thoughts? The only reason I care about the updates is Verizon swore they wouldn't send out a replacement until I took updates. I.e. their complaint was that I hadn't taken any updates.
Click to expand...
Click to collapse
It's normal and common that after flashing a TOT or KDZ that it says no updates for hours or even a day or so. Eventually, as long as you have an activated Verizon SIM inserted, it'll get updates. It won't without the SIM so if you already are using the SIM in a backup phone, that's another reason why.
If your USB were reliable, I'd suggest flashing the 47A KDZ, but I would recommend against it at this point.
roirraW "edor" ehT said:
It's normal and common that after flashing a TOT or KDZ that it says no updates for hours or even a day or so. Eventually, as long as you have an activated Verizon SIM inserted, it'll get updates. It won't without the SIM so if you already are using the SIM in a backup phone, that's another reason why.
If your USB were reliable, I'd suggest flashing the 47A KDZ, but I would recommend against it at this point.
Click to expand...
Click to collapse
Good point about 47A. Especially since their complaint was I hadn't taken any updates I want to be to say I actually took an OTA so I've got 24B on it now and I'll give it a day and see what shows up.
Glad to see you got it flashed back to stock.
Also, I should have asked this before, but are you using the original cable that came with the phone or a different one? It could be the cable itself is bad. Have you tried several different cables? Also, make sure you are not hooking up to USB 3.0 ports. I believe those won't work or don't work well with this phone. I could be wrong.
Or it could be the USB port is loose on your phone causing the issue. In that case, that's a hard one to get to work other than what you tried, which is jiggling and fiddling with it.
In any case, it appears you are good to go. Just because you haven't taken the latest OTAs shouldn't prevent them from taking the phone back IMHO but who knows.
Or, as @roirraW "edor" ehT stated, you can wait a few days and it should get the OTA eventually. I've usually found that after flashing TOT or KDZ, I get the notice right away.
iBolski said:
Glad to see you got it flashed back to stock.
Also, I should have asked this before, but are you using the original cable that came with the phone or a different one? It could be the cable itself is bad. Have you tried several different cables? Also, make sure you are not hooking up to USB 3.0 ports. I believe those won't work or don't work well with this phone. I could be wrong.
Or it could be the USB port is loose on your phone causing the issue. In that case, that's a hard one to get to work other than what you tried, which is jiggling and fiddling with it.
In any case, it appears you are good to go. Just because you haven't taken the latest OTAs shouldn't prevent them from taking the phone back IMHO but who knows.
Or, as @roirraW "edor" ehT stated, you can wait a few days and it should get the OTA eventually. I've usually found that after flashing TOT or KDZ, I get the notice right away.
Click to expand...
Click to collapse
Want to make sure I clearly understand. Now that I have the replacement phone up and running, I use the flash tool and flash 7b._VS985_LGUP8974.dll_-_From_stock_35B-47A_TOT_back_to_10B_using_this_DLL.7z to get back to back to 10B and then use Stump to reroot?
gospodinwizard said:
Want to make sure I clearly understand. Now that I have the replacement phone up and running, I use the flash tool and flash 7b._VS985_LGUP8974.dll_-_From_stock_35B-47A_TOT_back_to_10B_using_this_DLL.7z to get back to back to 10B and then use Stump to reroot?
Click to expand...
Click to collapse
No. That's only the .DLL. You also need the .TOT file, which I have the same place as that .DLL, and you need to extract them from the .7Z (7-Zip) archive with the free www.7-zip.org. See the last two posts of this thread http://forum.xda-developers.com/verizon-lg-g3/help/lg-g3-vs98547a-downgrade-t3354241/page3#post67731364.
Yes, Stump's brute force option, then TWRP Manager to put TWRP on, then wipe Cache, Dalvik/ART, Data, flash the ROM you want and then the appropriate Bootstack for the ROM you're flashing.
roirraW "edor" ehT said:
No. That's only the .DLL. You also need the .TOT file, which I have the same place as that .DLL, and you need to extract them from the .7Z (7-Zip) archive with the free www.7-zip.org. See the last two posts of this thread http://forum.xda-developers.com/verizon-lg-g3/help/lg-g3-vs98547a-downgrade-t3354241/page3#post67731364.
Yes, Stump's brute force option, then TWRP Manager to put TWRP on, then wipe Cache, Dalvik/ART, Data, flash the ROM you want and then the appropriate Bootstack for the ROM you're flashing.
Click to expand...
Click to collapse
OK finally got back to this. I have the flash tool and LGUP8974.dll and VS98510B_01.kdz. In the flash tool I see nowhere to specify a dll to use so that makes me a little nervous. The directory with the flash tool executable has other dll's in it already but none have the same name as the dll I downloaded. Do I just drop the downloaded dll in that directory and flash the 10B KDZ or is there something I'm missing? Clearly I'm erring on the side of caution here. Sorry for all the questions but I rather ask alot and get it right than damage anything.
My bad not the KDZ but this: 7a._VS98510B_03.TOT-4.4.2-KitKat-MD5_hash_inside-(official-will_get_OTAs_-_file_inside_is_mistakenly_named_Jellybean).7z
gospodinwizard said:
OK finally got back to this. I have the flash tool and LGUP8974.dll and VS98510B_01.kdz. In the flash tool I see nowhere to specify a dll to use so that makes me a little nervous. The directory with the flash tool executable has other dll's in it already but none have the same name as the dll I downloaded. Do I just drop the downloaded dll in that directory and flash the 10B KDZ or is there something I'm missing? Clearly I'm erring on the side of caution here. Sorry for all the questions but I rather ask alot and get it right than damage anything.
My bad not the KDZ but this: 7a._VS98510B_03.TOT-4.4.2-KitKat-MD5_hash_inside-(official-will_get_OTAs_-_file_inside_is_mistakenly_named_Jellybean).7z
Click to expand...
Click to collapse
It doesn't matter where the separate .DLL is, or the TOT. When you launch the tool you browse to the locations of them. If you already got the different megalock.dll and replaced the one in the installation directory then you're good to go. I don't think there's any danger, if something's not right it won't flash anything so there's no chance of damage from that anyway. There's directions for the TOT method all over including in the non-Verizon G3 General section. The instructions are the same no matter what device, just use that TOT and .DLL, and the driver's for the VS985 instead of whatever ones the guide you use specify. In all cases it's the same flash program and replacement megalock.dll as far as I've been able to tell.
roirraW "edor" ehT said:
It doesn't matter where the separate .DLL is, or the TOT. When you launch the tool you browse to the locations of them. If you already got the different megalock.dll and replaced the one in the installation directory then you're good to go. I don't think there's any danger, if something's not right it won't flash anything so there's no chance of damage from that anyway. There's directions for the TOT method all over including in the non-Verizon G3 General section. The instructions are the same no matter what device, just use that TOT and .DLL, and the driver's for the VS985 instead of whatever ones the guide you use specify. In all cases it's the same flash program and replacement megalock.dll as far as I've been able to tell.
Click to expand...
Click to collapse
Well see here's what is confusing me. I have the flash tool and have used it many times for KDZ's. However, there is no spot in there that lets me specify a particular dll AND it only browses for
.kdz and .cab files. .... .tot doesn't appear to even be an option. The only two files I downloaded were the TOT and dll for going back to 10 B that you pointed. It leaves me wondering if something is amiss with the flash tool I have. I am operating under the assumption that my objective is to flash the TOT file as I would previously flashed a KDZ but the flash tool I have wont even select a TOT file or a dll for that matter.
gospodinwizard said:
Well see here's what is confusing me. I have the flash tool and have used it many times for KDZ's. However, there is no spot in there that lets me specify a particular dll AND it only browses for
.kdz and .cab files. .... .tot doesn't appear to even be an option. The only two files I downloaded were the TOT and dll for going back to 10 B that you pointed. It leaves me wondering if something is amiss with the flash tool I have. I am operating under the assumption that my objective is to flash the TOT file as I would previously flashed a KDZ but the flash tool I have wont even select a TOT file or a dll for that matter.
Click to expand...
Click to collapse
The Flash Tool 2014 is for KDZs only. If you Google for "TOT method", you'll find instructions and links to a different flash program, and also to the megalock.dll that you need to replace the one that the program comes with when you install it. Find a TOT method thread and you'll get all the information and screenshots you need of what you need.
I'm getting a new g3 this week. I know the first thing the phone will do when I activate it is to do the OTAs. I want to root my phone. I want to know at which point do I stop the OTAs so I don't get stuck with unroot able version. I know the latest version, 6.0 is not root able. I do want to accidentally go to far.
Thanks
Don't take any OTAs at all if you can help it. It could come with 47A already, some other user's have recently.
Usually you can downgrade to 10B via the TOT method using the .DLL that's extracted from the 35B KDZ (both available from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Root is easiest with the Stump app on XDA with its brute force option and that only works on 10B, then use TWRP Manager to install TWRP, and that part is only that easy on 12B and below
@R-T-B has found evidence that if under your battery the model number has a K at the end like VS985WK, then you might not be able to downgrade at all, so no permanent root.
Kingroot works even on 47A but it's highly suspicious and deeply ingrains itself into your system even more than is necessary for root, and with it you have to reroot after every reboot, rooting requires Internet every time, and it might be sharing your private information in the background.
If you do try to downgrade and brick, especially if you have the "K" model number, @R-T-B has a new debrick thread in the General section with modifications to previously available methods to at least get the phone working back on 47A.
This my first lg phone so I'm not a noob when it comes to rooting, I'm unfamiliar with some of lg terms. I've had moto and Samsung in the past.
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
And yes, I have two threads on here. I have a thread to try and figure out out to unbrick a somewhat bricked g3 and this thread to make sure I don't do the same thing to the new phone.
Thanks
simpson1190 said:
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
Click to expand...
Click to collapse
The best way is the same (what I replied previous) no matter what version.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
So the only hard thing is if I'm past 10b and/or the device is already on MM.
simpson1190 said:
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
Click to expand...
Click to collapse
Yes to both. Highly unlikely it'll come with 10B, and very likely it'll come with 47A or at least 35B.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
simpson1190 said:
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
Click to expand...
Click to collapse
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
roirraW "edor" ehT said:
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
Click to expand...
Click to collapse
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
simpson1190 said:
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. [/QUOTE]
My Android File Host link...d has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
My Android File Host link at the bottom of the first post of that thread has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
ok i found your files and I"m downloading them now. I have downloaded the flash tool and it wants a username and password. found a work around that involves turning off the internet and resetting the date on the computer. Is this the best way to flash a tot or did i not download the correct tool?
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
simpson1190 said:
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
Click to expand...
Click to collapse
simpson1190 said:
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
Click to expand...
Click to collapse
LGUp doesn't work with the VS985. The second post of the LGUp thread details what to use for Verizon G3s.
Windows 10 works fine. As long as your PCB (printed circuit board) in your particular phone isn't v2 (you'd have to look in @R-T-B 's thread in the General section as far as where to look on the board to find the "2" or "1", etc), then yes the downgrade method is the same from 47A. If you happen to have a newer revision of the VS985 then putting Marshmallow on will keep it from being downgraded any longer. This is a fairly recent development (last week or two) that this has been noticed in such detail.
If it is revision 2 of the PCB, then you won't be able to downgrade from 47A at all.
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Dethfull said:
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Click to expand...
Click to collapse
Personally, I love my G3, but I'm with you. I won't buy another LG product until they lose their root/custom firmware unfriendly stance.
The Google in says "Google is your friend"
so, A friendly acceptable device, is being distributable by them?
We have years Forcing, imposing, root on all SIMPLY ALL these "friendly" devices.
How we believe on their phrase?
I only believe, the UNIX AND LINUX GPL ARE BEING PAID FOR THEIR "FRIENDISM".
Sent from my XT687 using xda premium