Looking for a little Guidance. Root & Rom - Verizon LG G3

After a fairly stressful 48hours trying to fix my tf700t after messing up rooting it I have learned to be more cautions. Im looking for for some advice before doing anything else with my LG G3.
Its already rooted. I did that almost immediately after getting it, but I haven't done anything else since. I would now like to upgrade to a quicker, cleaner ROM to help with some of the performance issues.
Here are my Specs.
Root, but not Custom recovery.
Model VS985G
Software VS98523C
Android 5.0.1
Questions.
1. Should I factory default first, then use the new one-click to re-root my phone.
2. Should I install a older version of TWRP first, then upgrade to a more recent software release, then upgrade to a newer TWRP before moving to a 6.0 based rom.
3. Any recommendations on a fast and stable ROM. I don't need anything flashy, but performance is important to me.
4. Will the new ROMS work with PDAnet USB teather. Which is very important and dear to me.
5. Will I still be able to use my Wifi hotspot. Also very important to me
6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Any help appreciated. I tried searching but couldn't really find definitive answers to my questions.

Hey, Thanks for asking the questions. here are some answers (p.s. i dont have my g3 right now will have it fixed by saturday.)
1. No, you dont have to, if you feel like you do go ahead. but once you get a custom recovery just be sure to back up the stock rom.
2. Since i have to redo my G3, i have no idea what the stock software my FrenkinG3 (The mobo died in mine so i bought a broken one and am putting the mobo in mine.) will have so, i dont know if i need to use the special bump'ed twrp first or not, ill let you know what happens, im am going to use the flashify to try to just flash the latest twrp 3
3. Before it broke, i really really liked Resurrection Remix rom. IMO it was the best. but for you probably just CM13. obviously i really don't know it has been since early January since i have had my g3. so maybe things have changed, but i cant assume they changed too much.
4. I dont see why not. If an Android 6 rom wont work try something like CM12.1 or a different Lollipop rom.
5. Yes, any custom rom you install, (at least in my experiance) will have the hotspot ready to go.
6. HAHAHAHAHAHAHAHA, probably not. i know it never really happened to me, but my buddy had it happen to him all of the time. He solved it by freezing one of the google apps.
If you have any other questions let me know. Happy to help any time.
p.s. Use Flashify (for root users), on the app store to flash recovery. i used it to update my recovery on my g3 many times. and will use it again soon.

6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Click to expand...
Click to collapse
I had the same problem, and it turned out to be a faulty aux port on the phones mainboard. It is a relatively easy replacement all you need is YouTube, something thin to pry it up, and a Philips head screwdriver size 0, haven't had an issue since and now the G3 properly recognizes headphones vs line in vs mic...

RussTdesign said:
1. Should I factory default first, then use the new one-click to re-root my phone.
Click to expand...
Click to collapse
You don't need to. Do it if you are super paranoid about clean installs.
2. Should I install a older version of TWRP first, then upgrade to a more recent software release, then upgrade to a newer TWRP before moving to a 6.0 based rom.
Click to expand...
Click to collapse
You should be fine installing the most recent version of TWRP (3.0.0?) It will be compatible with non-marshmallow versions.
3. Any recommendations on a fast and stable ROM. I don't need anything flashy, but performance is important to me.
Click to expand...
Click to collapse
I've tried several and my favorite is Jasmine 9.1
It is stock Lollipop based with moderate debloating for speed and is compatible with xposed and the LG G3 Tweaksbox.
Alternatively xdabbebs 2.0 is similar and many people love it. SkyDragon is similar to Jasmine but has a custom kernel for speed tweaks and other minor stock mods.
Personally I stay on modified stock because the stock camera is very good and you loose access to it on AOSP Roms.
If you want marshmallow I recommend doing a 47A install and using road warrior's debloating scripts. But MAKE 100% SURE you have Rooted and installed custom recovery BEFORE instill ng ANY Marshmallow Stock based ROM.
5. Will I still be able to use my Wifi hotspot. Also very important to me
Click to expand...
Click to collapse
Using a modified stock ROM should allow for Wifi hotspot.
Mine still works.
6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Click to expand...
Click to collapse
Xposed Framework + LG G3 Tweaksbox has an option for disabling the audio warnings (among other things...)
Best of luck. PM me if you want longer answers.

Related

Clean up my HDX 8.9 LTE from "Kindle-Soft"

Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
maluc said:
Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
Click to expand...
Click to collapse
You are playing with fire removing amazon apps from stock os. Before nexus and other roms came along I ran with a configuration similar to yours (no safestrap) and identified various amazon components that were annoying and/or aggressively ran in the background consuming resources. Many could be frozen but there were often unforeseen consequences. I had a couple scares with bootlooping and failure to boot that I was fortunate to recover from. Many 'kindle' components are baked into Fire OS and can't be easily removed/disabled.
My suggestion is to install a different rom. Nexus is very stable and gives a clean android experience. CM11/12 are great as well. Given you are on 1.3.0 I would suggest ditching Safestrap in favor of native twrp opening many more doors and, perhaps most importantly, a solid path to recovery should things go wrong. Although this is probably obvious, all remnants of Fire OS are removed with a different rom (aside from low level stuff you don't care about).
As a bonus you don't have to mess around with intalling Gapps with any of the roms currently available; it's already built in
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
maluc said:
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
Click to expand...
Click to collapse
To the best of my knowledge there is no explicit mobile support with nexus. If you need reliable 3g/lte then your best bet is to stick with stock until confirmed working 100% in CM11/12.
The 3.2.3 bootloader update posted here is flashable from within twrp or using a utility like flashify. However, I believe it assumes twrp (or cwm) is your primary recovery. I have no idea if it would work using flashify with stock recovery and safestrap. Perhaps someone more knowledgeable can comment on this. You might want to send a PM to ggow.
Set the 3.2.3 .bin file aside for now; you don't need it.
Last I knew (from this post) you had safestrap installed. Is that still the case? You really want to get safestrap out of the picture unless there is a good reason for retaining it. Make sure you know the correct procedure for uninstalling safestrap and restoring your preferred rom.
If you already have twrp installed *and* known good backup of your current system then you could move forward with the 3.2.3 bootloader update and then install CM11 which I believe works with a locked bootloader (recognizing it may not fully support 3g/lte). I believe the current CM12 builds do required an unlocked bootloader. You can unlock but it is not always a straight forward process.
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
maluc said:
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
Click to expand...
Click to collapse
There's an "unofficial" release of Nexus in the original thread with LTE compiled and it works quite well, alternatively CM11 LTE works great (on my Apollo) i'm sending and receiving SMS, haven't really tried calls yet but have used Facebook messenger to make and receive VOIP calls
EDIT: My bad, it's actually on Magic Beanz http://forum.xda-developers.com/showpost.php?p=59043532&postcount=73 which I would recommend over Nexus anyway (as long as you can get TWRP going).

About to buy an LG G3, PLEASE HELP!!

Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
ProFragger said:
Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
Click to expand...
Click to collapse
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Edde3d said:
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Click to expand...
Click to collapse
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Thanks so much for your help again!
ProFragger said:
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
Click to expand...
Click to collapse
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
ProFragger said:
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Click to expand...
Click to collapse
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
ProFragger said:
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Click to expand...
Click to collapse
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
epidenimus said:
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
Click to expand...
Click to collapse
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
ProFragger said:
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
Click to expand...
Click to collapse
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
ohlin5 said:
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
Click to expand...
Click to collapse
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
ProFragger said:
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
Click to expand...
Click to collapse
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
ohlin5 said:
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
Click to expand...
Click to collapse
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
ProFragger said:
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
Click to expand...
Click to collapse
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
ohlin5 said:
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
Click to expand...
Click to collapse
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
ProFragger said:
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about..
Click to expand...
Click to collapse
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
ProFragger said:
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Click to expand...
Click to collapse
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
ProFragger said:
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Click to expand...
Click to collapse
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
ProFragger said:
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
Click to expand...
Click to collapse
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
epidenimus said:
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Click to expand...
Click to collapse
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
iBolski said:
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
Click to expand...
Click to collapse
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
ProFragger said:
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
Click to expand...
Click to collapse
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
ohlin5 said:
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Click to expand...
Click to collapse
jfriend33 said:
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
Click to expand...
Click to collapse
Guys, horrible day of flashing.
GPS issues with both SD and Jasmine. Tried both stock and SD kernels, as well as 12B and 23C radios, no dice :'(!
Resurrection Remix, not enough options for me and zero GPS locks :'(!
BlissPop came the closest. Bluetooth worked, Xposed, had the options I wanted, but GPS is still not strong enough indoors, and there is an issue WiFi not autoconnecting on each boot :'(!
Long story short, I think I need to head back to 12B somehow. Can anyone please tell me how? I will TOT to 10B, but then, how do I get to 12B? I can't find the image for it anywhere! Please do help, I need a reliable
working phone tomorrow, porting my number into a new carrier...
Thanks in advance!
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
jfriend33 said:
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
Click to expand...
Click to collapse
Thanks for the quick response bud. I will try SD again, maybe, but for now, I liked how Stock felt out of the box which was 12B. I feel like with rooting, manual debloating, and maybe the CPU thermals mods, I would have a snappy 4.2 device.
I'm stupid, I did not Nandroid the 12B I had . Thought it would be like Samsung, each firmware easily available for download on the Internet to flash via the LG Flash Tools.
I will TOT to 10B tomorrow, but then question is, how do I upgrade or OTA to 12B? Would it give me options on which update to take? Or will it take me to the latest, which is 23C?
Appreciate your help or if anyone can! Thank you!

[SM-G360P] [ODIN] Official Samsung Firmware G360PVPU2APJ2

Hey guys I was able to take the time slooooowly download Stock firmware for our Prevail. Practically no support to this phone at all, but I've been working to change that as best I can. I am learning the ropes of ROM building and I have been able to make use of ASSSAYED Kitchen v.110 (Now upgraded to v1.20).
For those of you who don't know:
Odin tutorial
**DO AN ADVANCED WIPE IN TWRP BEFORE FLASHING. EVERYTHING EXCEPT THE EXTERNAL SD CARD**
Download Samsung USB Drivers (Go to this xda thread here).
Download Odin (Get it here) Extract to Desktop (Or wherever)
Download firmware to desktop (It's in .zip format and you can find it here). Extract .zip file to odin folder (again, or wherever). Extraction should yield G360PVPU2APJ2_G360PSPT2APJ2_G360PVPU2APJ2_HOME.tar
Right click Odin 3.10.6 and click on "run as administrator".
Click on AP and find the extracted ROM. Open it and it will take a minute to load in to Odin...Now make sure the 'Auto Reboot and F. reset time options are ticked and nothing else.
Make sure to be using a quality USB cord. Odin will recognize your phone being plugged in. It will say COM port number in the top left hand corner and added or removed will be in the log window. Once you are ready begin the flash press start.
Relax, It will take about 10 minutes to do it's thing. After the long agonizing initial boot process, you will be back to stock firmware PJ2 for SM-G360P
Hope it helps! So far there is no lollipop for our phone. Click here to check out all my uploads for this device. So far I have a TWRP port that actually works. (Must flash through Odin) an a Stock rooted deodexed busyboxed zipaligned rom of this firmware (Thanks to ASSAYYED Kitchen).
OLDER VERSIONS
OH1 Firmware
I flashed this back to my device in attempt to go stock but system status is still set to Custom just so everyone is aware. Not sure if it could be an error on my part.
just wanted to say thanks i have 2 of these phones 1 use for mp3 player/ play phone and the other my daughter has to use. ive tried a ton of twrps for this and everyone broke recovery. im dl ing the twrp and the rom you posted. ya there is no development on this phone at all. ive tried almost every rom i could to get it to lollipop with no luck. im going to try to get the theme store and the launcher swapped out with an updated version.. n5 s7 any is fine i just want to get it updated lol. ill play with it tonight and let you know how it goes. i appreciate the effort your putting in to this. i dont even have service to them i have a stubborn s7 that refuses to get rooted. i had no prob with the note7 but idk if i have some updated version of s7 but i cannot obtain full root. i need to have my audio mods at least. i have a good one with beats, dolby atomos and viper im going to try on the 360 as well. let me know if you would like the file. after i check if it works on this on that is.
Please stay tuned. Upgrading this thread to the most recent PJ2 firmware.
Thread updated to PJ2 firmware. I can confirm this will make your device status 'Official'.
Thank you!
I just wanted to say:
Thank you so much mate! An amazing job here, I had a broken rom on this device, and thanks to your PJ2 build; I now have a fully working device again!
Fixed the play store, play services, and all the ads and junk on this Textfree branded device (PE2 firmware confirmed). keep up the great work!
Thanks for posting this! I see your other files, would you mind going in more detail how to install the stock rooted deodexed version of this rom? How do you recommend unlocking the bootloader to install TWRP or can we just simply flash it with ODIN then install the stock rooted rom? Thanks!
EDIT: according to this forum looks like you just flash it. Do you recommend your 2.87 over the 3.02?
https://forum.xda-developers.com/ga...overy-teamwin-recovery-project-3-0-0-t3317381
EDIT 2: NVM found your other thread and looks like 2.87 is the way to go.
https://forum.xda-developers.com/ga...rom-stock-rooted-deodexed-zipaligned-t3464419
droiddude414 said:
Thanks for posting this! I see your other files, would you mind going in more detail how to install the stock rooted deodexed version of this rom? How do you recommend unlocking the bootloader to install TWRP or can we just simply flash it with ODIN then install the stock rooted rom? Thanks!
EDIT: according to this forum looks like you just flash it. Do you recommend your 2.87 over the 3.02?
https://forum.xda-developers.com/ga...overy-teamwin-recovery-project-3-0-0-t3317381
EDIT 2: NVM found your other thread and looks like 2.87 is the way to go.
https://forum.xda-developers.com/ga...rom-stock-rooted-deodexed-zipaligned-t3464419
Click to expand...
Click to collapse
Thanks! Just Odin it. Im running 2.8.7 and haven't tried any other versions lately. To install my custom rom, go here.
adrwill2000 said:
Thanks! Just Odin it. Im running 2.8.7 and haven't tried any other versions lately.
Click to expand...
Click to collapse
Awesome, thanks for keeping support alive for this phone!
I'd really like a custom rom for this phone i have to restart at least once a day or this ROM becomes unusably slow.. I mean atleast CM11
Hello. I'm Dave. I just got this phone (G360P Prevail LTE) and I'm pretty excited about it because it could sure use some stuff and I'm new to development and ROM porting. My goal is to bring great ROMs to the lower end phones that are sometimes forgotten in development. Right now I only have one good port under my belt, but it's a great one...PAC 5.1.1 for the ZTE Zmax Z970. Unfortunately, I used device and kernel trees that were already put together by another developer, so I'm not completely sure how to get started on putting trees together for this one. At least it's a Samsung, so mistakes will not be deadly, hopefully lol. There's a lot I don't know and this will be a hell of a learning experience. If anyone could fill me in on which devices that have some development going are most similar to this one, it would be a big help. I flashed the TWRP for the G360T1 before I found @adrwill2000's stuff since it has the same processor and specs and I'm sure you all know how that worked out...I guess I'll start by grabbing stuff for the device that our TWRP was ported from, unless you guys have any better suggestions. It would be best to start with trees from a very similar device. I almost hate to post this because it's very possible I will get nowhere, but I could sure use input from you guys that know this device well as to what my best starting point might be. Thank you.
I'm back to running H1 for now because it seems to be our latest that xposed is working on and imo this KitKat stuff sure needs some Gravitybox. Also, on mine, in J2, when I hit reboot it would reboot recovery. I was gonna fix it, but it's working in H1.
Scratch that...I found the Xposed updated for new 4.4s, so I'm on the deodexed, zipaligned j2 now. Thanks for all you've done with this, @adrwill2000...
It worked for me. My phone was bricked and I could not even get it to hard reset. Thank you!

Help!!! I am Confused!!

I bought a LG V10 today i dont know if its used or new (LOL) any way to find that out i checked IMEI says its orignal talked to people at LG USA they said its Original Here are my questions:
1) How to know if your phone is Legit like New + Lasting?( in my country they replicate used to orignal or fake to orignal)
2) How to Root LG V10? (i tried it with other phones i broke them)
3) Suggest Some Recommended Apps and ROMS?
4)I have seen a youtube video of xdadevelopers they were talking how you can overclock or under clock your device can i do that with my phone?
5)Last Question How can i myself from the infamous Bootloop? (Any Suggestion, Tricks Ways)
I am new here i need your help for not doing a rookie mistake....
1) Get the LG Phone Info app on the Google Play Market and as long as that shows "OK" in the Original info (the first box after you click the Get Information button) then your device is an original and not something that's been modified on a firmware level.
2) If you have Lollipop or Marshmallow rooting is fairly easy by comparison to Nougat. If you have Nougat on it already things are basically a stop - there is no working root for Nougat at this moment IF the device has been upgraded to Nougat using T-Mobile's OTA direct from them. Once that's been installed there's no turning back and no working root at this point but some devs are working on it, no guarantees they'll ever be able to create one.
If the device has Lollipop or Marshmallow on it you can get it rooted. The best course of action is to go from Lollipop to Marshmallow (the last Marshmallow build is 20l and that's an "L" there, lowercase, not 1 or i/I) and then what you'll need to do is get TWRP on it (that step is critical) then you would flash this modified update.zip to get to Nougat build 30b on it. runningak3d modified that update.zip file so it does NOT overwrite the recovery partition and you get to keep TWRP installed for flashing purposes. If you use T-Mobile's official OTA update.zip you'll be stuck, not able to flash anything including TWRP, or get rooted, etc.
So, again, the process is get to Marshmallow 20l, then get TWRP installed - at that point root is not necessary just to get the modified 20b update.zip on it. Then use TWRP to flash that modified 20b update.zip at which point it'll be Nougat, and THEN you can flash SuperSU with TWRP and you end up with a V10 running Nougat and rooted, that's the only method at this point.
runningak3d said he (or she, sorry, I just don't know) would try to create another modified update.zip which is pre-rooted so when installed you've got root/SuperSU ready to go but it's barely a minute to install SuperSU manually after flashing that modified 20b update.zip so it's not really a big issue there.
3) There are no custom ROMs for the V10 at this point, no Lineage, no AOSP, nothing really. There are some modified stock ROMs iirc but nothing that's totally custom and we V10 owners are still hoping some dev will take some time and create an unofficial Lineage build for the V10 based on Nougat (or even Marshmallow, I don't really care which Android version it's based on just that it's Lineage through and through). It seems pretty screwy that nobody seems to care about the V10 enough to have created a custom ROM but that's how it goes sometimes. The V10 is like an LG G4 on steroids in some respects, basically the same hardware overall with some minor differences (the second screen, of course, but I don't even use that on mine so I don't care about it at all).
I just wanted Lineage because it's so lean and efficient compared to any stock ROM and of course the potential for having a custom kernel with more governor support and other aspects is the big draw for me so, the hope remains that someone out there will take some pity on us woeful V10 owners and drop a Lineage build someday.
As for apps, well, that's entirely up to you and what you use your V10 for, and since nobody knows that but you then it'll be up to you to decide what kinds of apps you're going to be looking for.
4) Over-and-underclocking requires a custom kernel that allows for such things, and the stock kernel that's available (I think there was one custom kernel but it's just a modified stock one with limited additional capabilities) simply doesn't allow for such alterations. The V10 is quite fast on its own natively so, I can't imagine why someone would need to overclock it - I can understand WHY someone would WANT to do it, of course, but as for an actual need to do it, nope.
As for underclocking, that would save battery and be what I'd call a need in some respects, but again there just doesn't seem to be any developer out there that gives a damn about the V10 sadly. I wish I had spent more time learning how to create custom ROMs over the years and trick out some kernels as well using the provided source from manufacturers of these smartphones but I never did.
5) There is no way to prevent the potential bootloop issue which affects the G3/G4/G5/G6 (I saw one report so it could be bogus for the G6) and also the V10/V20 (seen two reports for the V20) and the Nexus 5x because it's a hardware manufacturing defect related to how the Snapdragon SoCs are mounted on the motherboards. There's nothing that you can do about it and there's no way to know for sure if the V10 you have will develop problems because of it or not, all you can do is use it and be done with it and hope for the best. Again, there is no fix and there's no way to know or prevent it from happening so, no matter what so called "fix" you read about or see a video about, it's all BS and best avoided.
My recommendation: since you just got the V10, go to LG's website and register the V10 in your name (might have to create an account) and then say you bought it in March, April, or May of 2017 (just a few months ago) and that will give you warranty protection through at least mid-2018. If you do that and it does bootloop on you, LG will replace it through the warranty period. Don't register it and you're out of luck if it does bootloop on you.
Hope this helps...

Sony Z2 Horrid Device

The Sony Xperia Z2 tablet has got to be the most horrible device in android history to root or install a recovery on it. The process and the complexity of it is just horrible. You daren't ever make the slightest change to a rom or anything in twrp as it just screws everything up on this device. I can't count the amount of roms i've put on it just to totally trash the device and you have to start from scratch. Either you put a new rom on, it wipes the recovery, you have to piss about using flashtool to flash some other ftf on just to get into recovery, then you have to then flash another tft to get root, the list just goes on and on. I don't even know why sony mobile even bother offering the bootloader unlock option in the first place, it's an absolute nightmare. It's basically you can have root with the official stock firmware, if you want a custom rom spend the next 2 weeks trying to get supersu installed on it. The most horrible device I've ever come across.
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
BabelHuber said:
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
Click to expand...
Click to collapse
I've tried Carbon and would love to use it but it just screws up the tablet after install and recovery gets wiped so you can't even go back to restore a back up. You then have to reflash using Emma then back into flashtool to reflash the tft to get recovery to work again because flashtool ends up reporting back that the current tft is not compatible with the device. It's a finicky device to root. It's got to be the worst out of all android devices. E.g my Samsung s9 had it rooted and flashed with a custom rom in around 5 mins. No matter what firmware is installed. Sony decided that after 23.1.A.575 or whatever rooting was not possible after that. Also every method on here telling you how to do it is different to each other and inconsistant. I tried 23.1.A.575 root for UK and it would not allow for twrp to be booted into. I had to use xperiafirm to download the Taiwanese version so I could get the batch script to allow recovery so holding down power on volume down would allow twrp to load. It's just a painstakingly horrible device to root to get something so simple. But yes your right probably best time to get rid and something different. Sorry for the rant it's just been a frustration for me.
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
BabelHuber said:
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
Click to expand...
Click to collapse
I've followed so many without much success. I tried the solution by kulvertti to the letter and the tab was having non of it. I think the problem also is that a lot of the links are dead to the specific tft you need to download so getting the exact version is tricky. The only one that has worked for me is the Taiwanese rom then using the recovery script by danalec to get Marshmallow flashed which is what I'm running now. So I made a back up today and thought OK let me try carbon because I can get all the nice customization options like being able to choose a dark theme for the settings menu instead of piercing white. What is it with manufacturers wanna make every thing bright and painful on the eyes. Anyway downloaded gaps wiped system etc installed rom and once it loaded the system was all unstable and lost root and recovery. So I give up now and have to accept I can only have marshmallow on it.
Danalec has a very simple root method for Marshmallow in the general section. This is one of the best tablets out there by far. Build quality doesn't come close with other brands.

Categories

Resources