Hello all,
Recently moved back to Android after a pretty unsuccessful stint with Windows Phone. Anyway, got the G3 (D852) for a steal but was disappointed to find some of the features of stock Android missing (multiple users, expandable notifications) from the stock ROM so wanted to go the AOSP/CM route, but I had some questions I was hoping someone could answer before I go ahead and do that.
1.) As I bought the phone new, it still has a warranty. Would flashing a custom recovery trip a counter like on some Samsung phones or can the phone be restored to full stock without the shop knowing in case I need to take it in?
2.) Are there any major bugs with CM roms? I read that there are some issues with audio recordings and camera quality. Anything else I should be aware of?
3.) Do features such as double tap to wake, the Quick Circle case, and knock code work with CM?
I think that's all for now. Thank you in advance for your help!
1) Theres a root flag checker in the service menu that detects if you have the su or busybox binary present on your device along with superuser.apk but if you download the firmware for the device and you do a full wipe using the flash tool it resets the check
3) Double tap to wake and knock code work properly with CM, Quick Circle can only be used to unlock the device unless you install a xposed module
Whats the feasibility of exchanging your D852 for a D855?
Hey, thanks for the super quick reply. Not likely I can change without paying quite the penalty so I'd prefer to just stick it out. I imagine there's not a whole lot of support for our Canadian model then? Seems strange to have a whole other version of the device just for us. :/
Related
Hey guys, sorry if this has already been answered somewhere else but I couldn't find it anywhere.
I bought a Galaxy Nexus a couple weeks ago and am loving it (except for battery life) and am interested in rooting it. But I have a few questions first:
1. What is the difference between unlocking the bootloader and rooting a phone. I know what unlocking a bootloader is, but I don't know much about rooting.
2. If I unlock and root, will I still be able to get updates from Google directly wihtout issues? Like, will I get the 4.0.3 update whenever it comes out even if I'm rooted?
3. Will my warranty be voided if I unlock the bootloader?
4. And if I do root it, what ROMs do you guys suggest I use? Which ones are the smoothest in performance and give the best battery life and customizations etc?
5. There is a new unlock/root tool made for the SGN, shown here: droid-life.com /2012/01/04/simple-galaxy-nexus-lte-rootunlock-and-unrootre-lock-tool-released/
Is it as effective as unlocking and rooting manually or does it have some drawbacks since it does everything for you automatically? BTW, thanks to whoever made that tool.
I know these are dumb questions but I'm new at this, so please bear with me. Thanks for any help in advance!
Peesashiz said:
Hey guys, sorry if this has already been answered somewhere else but I couldn't find it anywhere.
I bought a Galaxy Nexus a couple weeks ago and am loving it (except for battery life) and am interested in rooting it. But I have a few questions first:
1. What is the difference between unlocking the bootloader and rooting a phone. I know what unlocking a bootloader is, but I don't know much about rooting.
2. If I unlock and root, will I still be able to get updates from Google directly wihtout issues? Like, will I get the 4.0.3 update whenever it comes out even if I'm rooted?
3. Will my warranty be voided if I unlock the bootloader?
4. And if I do root it, what ROMs do you guys suggest I use? Which ones are the smoothest in performance and give the best battery life and customizations etc?
5. There is a new unlock/root tool made for the SGN, shown here: droid-life.com /2012/01/04/simple-galaxy-nexus-lte-rootunlock-and-unrootre-lock-tool-released/
Is it as effective as unlocking and rooting manually or does it have some drawbacks since it does everything for you automatically? BTW, thanks to whoever made that tool.
I know these are dumb questions but I'm new at this, so please bear with me. Thanks for any help in advance!
Click to expand...
Click to collapse
1) I have an app called All About Root which should answer the majority of all basic questions and even some advanced technical ones regarding root.
2) Yes, if you're still on stock and dont change/modify any of the stock apk/framework files. Once the OTA update finishes, root access will be removed and a stock recovery will be reloaded. Will have to fastboot flash the custom recovery back and set the permissions back on root (permissions are a topic in All About Root)
3) Depends on who is covering the warranty or another way to put it, who/where/how device was purchased.
5) I would always recommend learning the manual method. Once you load the android-sdk, which is needed for many customizations, the unlock is a simple command and learning adb/fastboot will be very useful in the future for most operations.
Hope that helps! I'm sure others will chime in with their opinions and experiences to cover any gaps I might have missed. Good luck!
1) Unlocking allows you to modify the kernel and flash custom roms. Rooting allows you root access to the OS. Root is the equivalent of an admin in windows, but in the context of android it gives you write access to the full device. Basically it allows you to access lower level system functions (ie droidwall is a gui for iptables which is a firewall).
2)My understanding is that if you unlock and root, you'll be running a custom recovery (clockwork). I'm not sure if that means you won't see the OTA or if it'll just revert to stock or it may not work at all. Perhaps someone else can explain, but frankly when you get to #4 I don't see any reason why OTA updates are relevant.
3) I think the bootload can be relocked so even if it does void the warranty it can be reversed. Whether or not they can tell that it has been unlocked I don't know, and if they wanted to find a reason to deny a warranty I'm sure they could find one whether or not it's unlocked. I'd be surprised if they denied it though since the nexus devices are important because they can be unlocked.
4) I've used Axiom pretty much since the day after I got my phone. Most of them are all the same 4.0.3 core just various modifications to 'improve' the experience. The one other rom I'd look at is kang's because it's based on CM9. Kernels are another issue from there - I've liked both leankernel and franco's. Note that you should check out the forums over at rootzwiki as their dev area seems more active than around here. The kernel is the main source of battery and performance boosts.
5) I would recommend attempting it manually. The most difficult part imo is getting the drivers installed and the device recognized by adb. From there it's just executing a single line to unlocked. Unlocking will wipe your data. I'll say it again...unlocking will wipe your data. I used superboot myself, but if you're going to a custom rom then getting root access is really only needed temporarily to get clockwork installed - any custom rom has root access already. Here's a link to superboot. I *think* you just execute it from your computer (its a batch file) and it will root the device for you. I'm not sure if it installs clockworkmod so the first thing you should do after booting is download rom manager and reflash recovery to be sure. Then you can use clockworkmod to move to a rom.
Happy flashing.
Hey guys,
yesterday I bought a i9192 in Germany (not officially sold here --> imported).
First thing it did was to update to I9192XXUBNB1. After that, I wanted to gain root access as I want to use different software that needs root (Tasker, Titanium Backup, StickMount, ...).
Unfortunately, there are many guides but from non of them, I was able to see if it really worked for I9192XXUBNB1 and which problem appear afterwards.
Can anyone help me to find a guide that defintively works?
I'm not sure what will happen in Europe if the Knox-Flag gets triggered with an imported phone but with all the Samsung-Sw on it and without Tasker, its note really funny to use the phone. So, if there is a way withoug triggering Knox, it would be great. And if not, well, let's hope I don't need the warranty ...
Thanks and greetings,
Matthias
You should not have updated your phone so fast. I9192XXUBNB1 seems to be a version not easy to be rooted. The easiest way is to actually install a pre-rooted knox-free rom. You have now installed a stock rom with Knox and it is impossible to install a pre-rooted rom without triggering Knox.
Here is the pre-rooted rom:
http://forum.xda-developers.com/showthread.php?t=2620621
Last reminder: upon installation of any non-official rom the Knox counter will be triggered immediately
Yes, well, I know now ...
But normally, first thing I do with new devices is updating to the newest version - in this case, this was a mistake.
As a result, I flashed the version cou mentioned, triggered the flag - and everything works fine.
Busybox installed, Secure Settings and Tasker is up and running.
As I'm from Germany, I hope there won't be any problem IF I have the need for warranty.
Thanks,
Matthias
matmike said:
Yes, well, I know now ...
But normally, first thing I do with new devices is updating to the newest version - in this case, this was a mistake.
As a result, I flashed the version cou mentioned, triggered the flag - and everything works fine.
Busybox installed, Secure Settings and Tasker is up and running.
As I'm from Germany, I hope there won't be any problem IF I have the need for warranty.
Thanks,
Matthias
Click to expand...
Click to collapse
Yes we all should blame Samsung for making the stupid Knox a default installation instead of optional. Also rooting of newer firmware is more and more difficult.
In general, you're right as the new software "features" really make bad problems for the experienced users who want to use advanced functions.
But from a different point of view, I partially can understand what Samsung does: IF they have a problem with more cases of warranty with rooted/modfied devices that go back to original directly before sending them back to Samsun, the thing they did is the only way to solve that - know if a phone was modified.
Personally, I work in automotive industry and there is a similar problem: Some people alwas try to tune their cars (in more or less senseful ways). And if there is a problem with a part of the car, they just go back to the original state like "what, me, no modification at all". In the end, this would cause costs for the company. So why not implement just a flag that shows "Modified" so you can reject warranty for parts that get problems with tuning (engine, axles, clutches) if tuning caused the problem. The rest of the parts that is not involved (radio, body, ...) is still valid for normal warranty.
With my samsung phone, that means: if there is a defect, Samsung has the chance to check if the modification caused the problem or not and eventually reject a repair. Of course, "With great power comes great responsibility" so let's hope Samsung uses the power in a good way without rejecting every failure of a modified phone. If the button on the front falls out, it is very unlikely that wrong software caused the problem
Greeting,
Matthias
Hope this the right place to post - please let me know if not.
I have the Sprint G3. I rooted (being a first time rooter at that time) within a few weeks of getting the phone. Frankly, I don't recall how I rooted it, but I think it was using Stump'd. In any case, root went fine, installed, SU, and been using some of the Framework apps like tweaksbox.
Okay, here's what I need some help with:
I think I need to unroot the phone, return it to factory stock, and then reroot before flashing a ROM to it. Is that correct?
I've seen a couple of threads here with instructions, but I don't follow/understand much of the terminology. Hence, is this page good to use to help me - http://lgg3root.com/lg-g3-root/how-t...nbrick-lg-g3/?
Secondly, once returned to factory srock ROM, will I have to OTA update to the most current version for Sprint before rerooting? I think I've read that the current stock ROM is not yet rootable?
Third, I really want to flash a ROM because I think it will result in a lighter weight ROM to conserve battery power and because I really want to theme the phone beyond what I can do now rotted with icon packs and tweaksbox. Is the CM ROM lighter weight and will I realize better battery performance?
Lastly, I'm hesitant to install a custom ROM because I'm afraid of losing phone, data, sms, gps services. I think this after reading the custome ROM threads and see complaints regarding users not having services available or connectivity issues. Is this a legit concern or am I overthinking this?
Thanks in advance for your suggestions, tips, and feedback.
JMak00 said:
Hope this the right place to post - please let me know if not.
I have the Sprint G3. I rooted (being a first time rooter at that time) within a few weeks of getting the phone. Frankly, I don't recall how I rooted it, but I think it was using Stump'd. In any case, root went fine, installed, SU, and been using some of the Framework apps like tweaksbox.
Okay, here's what I need some help with:
I think I need to unroot the phone, return it to factory stock, and then reroot before flashing a ROM to it. Is that correct?
I've seen a couple of threads here with instructions, but I don't follow/understand much of the terminology. Hence, is this page good to use to help me - http://lgg3root.com/lg-g3-root/how-t...nbrick-lg-g3/?
Secondly, once returned to factory srock ROM, will I have to OTA update to the most current version for Sprint before rerooting? I think I've read that the current stock ROM is not yet rootable?
Third, I really want to flash a ROM because I think it will result in a lighter weight ROM to conserve battery power and because I really want to theme the phone beyond what I can do now rotted with icon packs and tweaksbox. Is the CM ROM lighter weight and will I realize better battery performance?
Lastly, I'm hesitant to install a custom ROM because I'm afraid of losing phone, data, sms, gps services. I think this after reading the custome ROM threads and see complaints regarding users not having services available or connectivity issues. Is this a legit concern or am I overthinking this?
Thanks in advance for your suggestions, tips, and feedback.
Click to expand...
Click to collapse
First lets start with returning to Stock ROM. No, no you definitely do not need to return to stock factory ROM to flash a new one. Since you already are rooted all you need is a TWRP recovery.
To flash TWRP recovery to your device (Sprint G3) use this thread:
http://forum.xda-developers.com/sprint-lg-g3/orig-development/bump-unlock-lg-g3-twrp-sprint-t2900588
It's very easy for a begginer to achive this. If you don't want to use adb, fell free to download flashify and flash the downloaded TWRP image from thread above with it.
It's even easier with flashify.
Yes CM ROM is lighter, closer to stock android, not the LG one. If you really want better battery experience you should also look up different kernels, different governors, more adavanced stuff, nothing too much.
You don't need to be scared of flashing ROMs. It's a very basic task these days.
Losing data, calling ability or other thing is very unlikely. Of course mistakes happen so be careful. First thing to do before flashing anything on your device after instaling your TWRP recovery is to do a backup.
ALWAYS DO A BACKUP OF ALL IMPORTANT PARTITIONS ON YOUR DEVICE.
To get your custom ROMs, including CM look up these:
http://forum.xda-developers.com/sprint-lg-g3/orig-development
http://forum.xda-developers.com/lg-g3/development
Also be careful to flash things made only for your device (Sprint LG G3).
Very helpful and thanks.
To show off my noobness... Do custom ROMs have customer kernels or do I install a customer kernel as well as a custom ROM?
Yes, they do come with custom kernels.
But you could change kernel for some other one if you wish for.
I personally use Blisspop 3.7 on my LG G3 D855 with kernel that came with it 777 by 777jon.
Thanks, now to twrp, flash new rom and install cm 12 theme. Fingers crossed I dont go ham and brick the device.
I've always rooted my nexus phones and installed the bevy of apps out there but with my 5X I'm going to go no root for a while and see if I can survive... I need app replacements for a few apps, any suggestions would be welcomed
- viper4android
- volume booster that would come in effect if flashed a kernel
- colour control
Thxs
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
drose6102 said:
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
Click to expand...
Click to collapse
Fair enough. I'm in the same boat waiting for certain the process for root and encryption, guess I'll sit tight and just work with what I have. As for viper4android, probably my #1 app, love the sound quality that produces.
I'm trying rootless too. I mainly rooted in the recent past (Sam Gal S4) to use TiBu to freeze all the VZW/Sam crap. Since thats not there now, I think I'm good.
I am also going rootless for now, not sure if I should unlock bootloader or wait..
Will be rooting here soon. Missing the root life from my S4 and the likes of Viper4Android.
I honestly think there's no reason to NOT root at this point. It's SO EASY to return back to stock using factory images, I been rooted with twrp for a week and the phone has been working GREAT fast and smooth. Only problem is for some reason wells fargo app isn't compatible with marshmallow
What could go wrong? all you have to do is flash chainfires modded boot image and viola, easy as pie.
If you wish to root, go right ahead! The procedure is simple and documented clearly in Heisenberg's [GUIDE] Unlock/Root/Flash for Nexus 5X
The same guide also explains how to return to stock (by flashing a factory image).
It's all explained in the guide. It is worth noting that the root process requires one to flash a modified boot.img, which is currently available only for the MDB08I build. So you can only root if you're on that build or can upgrade to it...
Hopefully a 'cleaner' root procedure (with encryption support for those that wish to have it) will emerge, but there are no guarantees.
Also see: A Look at Marshmallow Root & Verity Complications
one reason I haven't rooted yet is the little updates that always come quick after a new release. They will come, and spending an hour fastbooting is just getting old for me. I think I've turned into an old man, I'm just too lazy to wipe/flash/ download set up all over again. Things have come a long way since the N1.
Absolutely though, when exposed and gravity box are good for 6.0 I'm in.
I've had a phone upgrade available to me for a while now and have had a very positive experience with the G3. I want to get a G4, but I'm not getting the impression that the VS986 has been all that easy to get things unlocked on. Before I throw down money on it, I'd like to get some more information about the status of some things that I haven't found a lot of clear information on in this forum:
1) Is their a way to root the most current OTA for it (i.e. the version of Android that would be on it if I walked into a Verizon store right now and bought one)?
2) If rooting is a thing, has anyone got Xposed working on it? With that, are there any must have modules for the G4 (similar to G3 TweaksBox)?
3) This one looks the least promising based on what I've seen here but is probably the most important: has anyone got custom recovery (preferably TWRP) working on the VS986? Don't want to mess around with it too much without having backups.
4) Are there any good ROMs for it? I've just been using a debloated version of the G3's stock ROM for quite a while now and wouldn't mind using something similar (although stepping out and trying an AOSP ROM would be cool, too)
Thanks in advanced.
1) + 2) is a yes (root is available, and xposed via flashfire)
3) + 4) a no go right now (at least for the Verizon version)
Ya, verizon bootloader has stayed locked. But if you keep an image on your internal drive, you should be ok to reflash. We are also waiting on a 13B KDZ incase things get bad and you don't have a good image on phone, but hopefully it won't be too much longer.
Edit: I really love the G4, especially after the 13B update. Fixed my touchscreen issues and feels snappier with a few other improvements. The one one one thing I wish it had was a fingerprint scanner. WTB V10's fingerprint scanner...
WrittenImprov said:
I've had a phone upgrade available to me for a while now and have had a very positive experience with the G3. I want to get a G4, but I'm not getting the impression that the VS986 has been all that easy to get things unlocked on. Before I throw down money on it, I'd like to get some more information about the status of some things that I haven't found a lot of clear information on in this forum:
1) Is their a way to root the most current OTA for it (i.e. the version of Android that would be on it if I walked into a Verizon store right now and bought one)?
2) If rooting is a thing, has anyone got Xposed working on it? With that, are there any must have modules for the G4 (similar to G3 TweaksBox)?
3) This one looks the least promising based on what I've seen here but is probably the most important: has anyone got custom recovery (preferably TWRP) working on the VS986? Don't want to mess around with it too much without having backups.
4) Are there any good ROMs for it? I've just been using a debloated version of the G3's stock ROM for quite a while now and wouldn't mind using something similar (although stepping out and trying an AOSP ROM would be cool, too)
Thanks in advanced.
Click to expand...
Click to collapse
The bootloader is still locked.