I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
sashusmom said:
I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
Click to expand...
Click to collapse
Most of your questions have been answered before but I will try my best to re-answer them. I will try to clear up any misguided understanding you may have.
-Does it update over internet data connection, or just wifi?
+It updates over a internet connection.
-What is the safest build if I want to possibly unlock the bootloader when it is released??
+We don't know yet. Stay on the version you're on for now.
-4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
+If you don't know much about what it does it's best for you not to worry. Yes, it's fine to leave safestrap alone.
-5. Block OTA updates with #4- Does this still work on the latest, safest build?]
+Yes, it works. The only time it may change up is if Amazon pushes a update with different package names or functions.
-Is there any way to BU (Back-up?) original firmware before installing HDxposed stuff and google apps without safestrap?
+No. I'm not aware of any other way to backup the stock rom.
-Can you just re-install a manual update to recover if things go southafter reversing all the apks, modules, root, etc. after a factory reset?
+You can't re-install a update. You can factory reset it.
-To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
+There is no need to uninstall play store before a factory reset because the reset wipes it out. You should un-root via SuperSU and remove my ota block. (I reset while root but was unsure how safe it was. It did work out in the end without issue.)
Keep the wifi off once you undo the ota block and then factory reset so you don't update. Once the reset is done, re-install the blocker. I'm not sure if you need to remove safestrap before a factory reset.
To make clear:
If you install a ota blocker it's good to check that it works by being connected to the net and then going to Settings->Device->System Updates->Check now. If it says Last update failed it is working else it is not.
The current roms for the hdx require Hashcode's safestrap. But to get the rom's working you need a backup of the stock rom or you could use the backup he provided. Once a slot is made you would install the rom zip to the slot.
I believe safestrap works be emulating a new system/data/cache partition in a file as a full rom to the bootloader. I recommend blocking ota before you make a backup or installing a basic stock rom. If you create and install the stock rom to a rom slot without blocking ota, the amazon system files are still in place to call for a update and hand it off to the system and bootloader.
Safestrap is safe as long as you do not touch the stock rom but only to make a backup of it.
If you don't feel comfortable using safestrap then don't.
Quick word of advise, you should include the version of your device when asking questions for that version. I'm guessing your on 13.3.2.4, the current latest.
Also I highly recommend staying on your current version and not moving forward.
Last thing, give this a read.
I hope I answered your questions as clear as possible.
Anybody else please clear up anything I missed.
Also good luck with your device and play safe.
Thank you so much Faznx92 for reinforcing all that I read ( lots in a short time period). I didn't want to mix up the info I read from the beginning of the year to where this tab is now. You did clear up anything I was unsure about. Thank you! And safestrap- I am not comfortable with it at all- there is no safestrap for my Mega, all my other tech toys have unlocked bootloaders. So I have absolutely no experience with this custom recovery. I am used to CWM and TWRP. Totally comfortable with them, although I have to admit kitkat twisted my arm to try TWRP since that was the only way to flash those roms on a lot of tablets and phones. Now I am partial to that. So I won't say no to safestrap, just now when an unlock is so close. If a safestrap was released for my Mega, I would definitely give it a try.
Oh, I know to report what build I am on when asking questions- that's just polite and informative, right?? But I am not getting this tab till tomorrow, at least that's what tracking says. So I don't know yet. When I check the build I will post back and let you know what they are shipping now with. Hopefully it is still rootable and eligible for unlocking the bootloader when that is released. That is very exciting!
I give you credit for reading my epic long post, and thank you for taking the time to address my concerns. I appreciate it! I'll check back in tomorrow afternoon. Mail comes late where I am.
Your link was the First thing I read on this forum!!!! Which is why I am sticking with what I am comfortable with. Also, in my case I only learn by doing. But I have always realized that hacking leads to problems sometimes. My motto is stay calm, and reach out for help. Panic doesn't solve anything. And if you are hacking your only phone that you rely on, be prepared to go buy a cheap prepaid phone to bail you out till you straighten out your expensive semi brick! lol. I've gone from holding my breath when hitting go, to just being curious on how to do stuff and finding out how things work. I guess I'm living life backwards!! I can afford it at this point in my life.
Just received my kindle HDx 7 from Amazon.
So, I placed this order 1 am Wed. morning- the sale must have been on PST. Took free shipping- non prime. Received on Friday around noon. Way ahead of the promised date.
The build received was 13.3.2.1. Sim chip was installed and connected to the internet, so I took it out as a precaution even though it is not yet asso. with an account. Skipped wifi set up till I get OTA updates halted. Now it's time to play!
I Really like the size of this tablet.
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
sashusmom said:
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
Click to expand...
Click to collapse
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Faznx92 said:
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Click to expand...
Click to collapse
Thank you! I will hold where I am then. I guess since I bought it from amazon- an account I already had there- when I connected to wifi it sort of registered itself and associated it with my amazon account by Magic!!:silly:
I do have to say just using the native kindle OS, I am not a fan. I will be installing the HDxposed modules and google stuff. :fingers-crossed:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
jimyv said:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
Click to expand...
Click to collapse
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
too much
sashusmom said:
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
Click to expand...
Click to collapse
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
jimyv said:
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
Click to expand...
Click to collapse
No safestrap. I have a 32 GB. Is the internal partition for installing apps tiny on this tablet? I got the 32 gb so I wouldn't have this problem. Stock other than being rooted and having the HDxposed modules with google market installed. That might be taking up the room.
I have 1.1 GB of apps, system apps are close to 397 mb. I have 21 GB free.
************************************************************************
Must have been a space problem. I deleted AngryBirdsSpace and was able to install Adobe flash and Cerberus. Milk music still will not install, so don't think that is the issue with that one. It did install last week on my Note8 and my Mega so maybe because it's a samsung app??
Will Titanium BU work for moving apps to the sd card on this device? And free up space that way?
I can't seem to find the move to sd card on a long press with tit.BU, so I guess not.
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
themilkboy08 said:
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
Click to expand...
Click to collapse
What?
I have a Galaxy Light, and I'm fairly knowledgeable about the device. But I don't understand gibberish. You need to tell us exactly what you did, and try to speak in English without typos.
Ok
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
themilkboy08 said:
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
Click to expand...
Click to collapse
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Ok
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
themilkboy08 said:
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
Click to expand...
Click to collapse
Don't use T-Mobiles firmware on your MetroPCS phone.
This is what you need to do.
And for the love of all that is good in this world, next time DO A BACKUP before flashing things. You installed TWRP, which gives you the ability to make a complete backup of your system exactly as it is at that point in time. If you had done a back-up before you screwed up your phone, it would have taken you but a few minutes to unscrew it.
I apologize for being harsh, but it seems to me like you really need to read and research a lot more. I always (well, usually...almost bricked my tablet the other day) read everything I can find about something potentially risky before doing it. Let this be a learning experience for you. Read as much as you can, understand what it is you are actually doing rather than just following some guide, and if you don't understand, just ask. I and most of us here would rather you asked a noobish question instead of going blindly ahead and screwing your phone up. Playing around with root and recovery and flashing without understanding it is like thinking you can perform open heart surgery with a meat cleaver because you've seen every episode of ER, Scrubs, and Grey's Anatomy.
thanks
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
themilkboy08 said:
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
Click to expand...
Click to collapse
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Ok
Ok, and with the back up download how do I get the in twrp. Should I put it in a zip file or leave it how it is
ok im a retard
Planterz said:
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Click to expand...
Click to collapse
ok so i cannot figure out how to do this.
i have the sgh-t399n galaxy light- with no os installed, i have twrp on my phone. and i have a backup a sd card. but when i go to restore in twrp the backup isnt there, and ive tried going threw the file options to move it to where is it suposed to go but no such luck. i thought maybe a terminal command would work but i have no clue what command to use. if you could help one more time that would be awesome
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
fddm said:
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
Click to expand...
Click to collapse
Ugh... I own a t399n and I'm doing some real development on it. . I've made a stock odex and deodexed rooted zip files for the t399n and haven't posted them yet. . If you're in a bad way still hit me up and I'll have you up and running in no time. Fun things coming for metro users. Who says you have to pay for a high end device to have a high end device? He he he....
Do you have a backup I bicked my samsung galaxy light metropcs then I unbricked it by restoring a backup for the samsung galaxy light that I found online. Search fresh backup for samsung galaxy light sgh t399n.
Planterz said:
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Click to expand...
Click to collapse
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
reholli said:
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
Click to expand...
Click to collapse
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Planterz said:
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Click to expand...
Click to collapse
And the age of the post, with respect to your attitude, is relevant how?
reholli said:
And the age of the post, with respect to your attitude, is relevant how?
Click to expand...
Click to collapse
I just love getting an email alert at 4am because someone quoted me to post absolutely nothing of substance.
It's relevant because IT WAS A YEAR AGO! I don't remember why I was so cranky that day. I did apologize to him for it. Did you notice that I also still did my best to help him? Do you have a solution to his problem? Does he even still have this phone, given that it was a year ago? If you want to fixate on my posts, fixate on the hundreds of times I've been thanked for helping others, especially going above and beyond helping people find the perfect device for them. I'm not here to be grumpy, I'm here to help people, and get help when needed. Why are you here? To pester me? Look, I respect my elders, and you're clearly older, but at the same time don't presume to talk down to me. Try reflecting on yourself and your motive in making a useless post, bumping a thread dead for several months (a severe breach of netiquette), purely to insult another member.
Come to think of it, my email alert wasn't because I was quoted (I have that feature turned off). I got the alert because I'm still subscribed to this thread, having done so in case there were new posts that might enable me to help the OP. I suppose I should unsubscribe, giving the fact that nobody has posted anything of use or substance in 7 months or so.
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!