Many of my friends root their phones to get more apps with less restrictions. But there is one problem coming along with it, the device will not be guaranteed to be repaired once it's rooted. So, I haven't rooted it until now.
Related
I recently had a lot of updating problems after rooting my phone and deleting some unwanted applications. The supposed method of un-rooting which is to use Update Service or PC companion to repair or re-install the software back to its original state does not work for everyone. In fact, there are lots of folks I discovered trolling through different forums who experience the same hazards. This leaves me feeling that it might depend on whether you bought the phone sim free or you got it subsidised by a mobile carrier. Its possible the contract phones are prevented from updating after rooting in a bid to stop de-branding.
Well, its just my thouhgts. What do you guys think is responsible for this anomaly in unrooting. I had to flash my phone back to the generic uk firmware with Omnius to get it to update again. As things stand I will not be rooting my phone again.
Love to root
I rooted my e10i for 3times and reverted back with SE PC companion to its original state without any difficulty. My only problem after rooting was, the system was not stable. frequent reboots were happening(looking forward to fix that). Still i love to root again for these three things.
1. for deleting SE favorite apps.
2. for paid apps( which not yet available in my country)
3. Enabling wifi hotspot
[email protected] said:
I rooted my e10i for 3times and reverted back with SE PC companion to its original state without any difficulty. My only problem after rooting was, the system was not stable. frequent reboots were happening(looking forward to fix that). Still i love to root again for these three things.
1. for deleting SE favorite apps.
2. for paid apps( which not yet available in my country)
3. Enabling wifi hotspot
Click to expand...
Click to collapse
You misunderstand the point of my post. It was not to examine the pros and cons of rooting. I know rooting brings a lot of added benefits and functionality to the phone. I too rooted to use wifi tethering. My point is that rooting might not suit all phones. My argument, that it might depend on whether you got the phone sim free or through a contract.
It seems that rooting is making it problematic for upgrading of phone irrespective of locked or SIM free as is under discussion in the latest firmware thread. But the interseting point of this thread is zodiac100 has updated his phone through OMNIUS.
So zodiac100 will you please describe tthe process of upgrading through Omnius in detail or point us to the thread (English) where it is detailed in case some of us may find it useful now or in future.
Edit : I have read your advice about flashing by Omnius in another thread. Thanks for that. In Omnius site I couldnot find E10i phone but simply E10 with no picture. Is it the same phone?
Am i really need to root to manage the ram usage? I mean my problem is that when i read something with adobe reader than i search after something on the web and after it i return to my pdf file the adobe reader is fully closed and i need to search where is was in the doc.
I personally see no downside of rooting tbh, aslong as your confident in actually doing it, its all totally reversible, and working for a mobile phone company myself, I doubt the repair center would ever know it was done , should you need to send away in warranty
ive got 3 galaxys (2 i9000 and one 9100) all of them rooted and got problems that need service center - they never refused repair knowing that phones are rooted - i always got them repaired without root and with latest firmware upgraded
root is totaly reversible anyway
bobekk said:
ive got 3 galaxys (2 i9000 and one 9100) all of them rooted and got problems that need service center - they never refused repair knowing that phones are rooted - i always got them repaired without root and with latest firmware upgraded
root is totaly reversible anyway
Click to expand...
Click to collapse
I also had this I broke my digitiser and I even asked the repair team if it mattered I rooted and he said it was fine.
Plus there is a very easy root method and you can still stay on your stock ROM and kernel so you can manage ram with no downside.
Hello everyone,
I am very happy that I finally found this awesome forum, now I will able to learn more about my phone and android in general and help others just like I used to do before with my previous iPhone (OS). I used to jailbreak easily and enjoy all the features that I could find for the iphone. However, before 6 months I decided to switch to Android and got Samsung Galaxy Note 3 from Sprint, updated to 4.4.4. I absolutely love the device and never think to return to iPhone until I learned that rooting the Samsung will void the warranty that make me to reconsider another android phone other than Samsung. However, this isn't my concern right now, I have questions any help, even a small one would count to give me ideas and solutions.
I am new to rooting my phone (Never done it yet), but I am certain that I would want to do it because I want to change my device ID. I have noticed some apps from Play Store, will ask to pull my unique device ID and based on that they can store my information on their server no matter what I do, they will recognize my phone via device ID. I have tried these methods and they both failed.
*I tried to completely clean my phone from any data or history related to that app, I even change my account ID (email).
*I tried to use VPN from 5 different countries.
My phone was easily recognized by those app and they even retrieve my data that is save on their server. Note: most apps will pretend that after you uninstall and install that it doesn't recognize you as old user, but it does (Tested). I really have concern and I consider this to be a challenge.
I want to know:
1- Am I able to root my phone on version 4.4.4 and if so will it void the warranty from just trying to use the device ID feature?
2- If I do root the phone, just by rooting does that mean I am blocked by Samsung from getting any new updates and other apps updates?
3- For device ID, if I change my device ID for good and keep changing, will that affect me negatively anyhow, I mean samsung will notice and cut updates?
4- If I am prevented from having these updates. Can I download them manually and install them using my laptop.
I am sorry for my English and for being new to Android world. I would appreciate any kind of information that could help me. either by replaying or providing links.
Thanks
Edwardo
Edwardosd said:
Hello everyone,
1- Am I able to root my phone on version 4.4.4 and if so will it void the warranty from just trying to use the device ID feature?
2- If I do root the phone, just by rooting does that mean I am blocked by Samsung from getting any new updates and other apps updates?
3- For device ID, if I change my device ID for good and keep changing, will that affect me negatively anyhow, I mean samsung will notice and cut updates?
4- If I am prevented from having these updates. Can I download them manually and install them using my laptop.
Thanks
Edwardo
Click to expand...
Click to collapse
Edwardo,
Welcome to XDA! We're a friendly bunch here. I wanted to start off by saying that I appreciate how much information you gave in your first post. It is very nice to have enough information to truly help you. Now, onto your questions:
Rooting on 4.4.4
Unfortunately, there is currently no way to root the 4.4.4 version of the phone without tripping KNOX. KNOX is just the "switch" that says whether or not your phone software has ben tampered with. Technically, your warranty is void once you tip KNOX. In practice, though, Samsung doesn't really care if your KNOX is tripped. If you need to claim your warranty (i.e. broken screen, stuck button, etc), you can do so with a tripped KNOX and they won't even blink an eye.
In terms of "how to root," this thread has a very good method for gaining root access.
Future Updates from Samsung
Gaining root access should not affect future updates from Samsung or Sprint. If you end up going the "Custom ROM" route, you would have to restore back to the "stock" ROM before updating, but that is relatively easy.
Device ID changing
Unless I'm mistaken, there are two primary ways that apps identify you: Device ID and a proprietary (facebook, google, etc) login. It'd be obvious if the app is asking for a login, so the Device ID (UID) will be the one that you're wanting to change.
I've only used Titanium Backup to change my UID (you'll need to buy the "pro" version to unlock that capability), so I'm not sure of other methods, but I know that TiBu works.
The main updates (i.e. 4.4.2 to 4.4.4) to the phone will not be affected by changing your device ID. The only thing that could really be affected by it would be your Samsung Account. This is what updates your Samsung Apps. Most of these updates will be security-related (in my past experience). I doubt that the ever-changing Device ID would negatively affect it, but it's a possibility.
Manual Updating vs. OTA Updates
One great thing about XDA is that we have tons of resources to help others with their phones. If you do ever have issues with your phone, you can always restore a fully-stock ROM. Once you get used to flashing ROMS to your device, updating becomes trivial.
Here is one example of a "full restore" that will bring your phone to a completely stock state (even if you were on an older version). This thread has another one.
Hopefully this adequately answers your questions.
-Topher
topherk said:
Edwardo,
Hopefully this adequately answers your questions.
-Topher
Click to expand...
Click to collapse
Big thanks for the warm welcome and answering my questions. You have highlighted some points, I did not think about, if I change my device ID, I might not let Samsung recognize my device and get some updates, as you said it is possible, but I am very certain I will have to do it. I never use apps that force to access (Facebook, google, etc) I immediately delete them. So yes, those apps store my data based on the unique device ID.
I am going to read the links you provided and slowly I will root my device and download the app you have recommended.
Again thanks!
Please, I hope somebody doesn't start berating me for not reading XDA posts about my Verizon Galaxy Note II more thoroughly. I have read many over recent years and been saved by quite a few during the hacking of my SCH-I605. Furthermore, I've been working in software development and network administration for decades now, so please don't somebody suggest I not mess with rooting my phone, custom recoveries, et cetera. I am here asking questions to make sure I don't hard brick my phone. Not asking resulted, about two months ago, in almost succeeding at Kobol's very interesting "short the tiny resistor" mode of getting out of a boot loop. I have a fully functioning phone now running rooted Kitkat and it's a sturdy platform, runs really great after I melted most of the bloatware and froze the rest (in case I ever need it), but I'd still like to move on to Lollipop and there is only one means for doing so which I know of (CyanogenMod), which I think may be problematic unless I am able to reflash an earlier ROM with unlocked bootloader.
The basic question I need verified is multi-part but basically boils down to this:
1. Is it or is it not true that if one is at baseband version I605VRUFND7, the bootloader is locked and one cannot install a custom recovery? (I think I read that in a few places anyhow.)
2. Is it or is it not possible to flash back to I605VRALJB from rooted I605VRUFND7?
3. Is flashing back to I605VRALJB, then installing TRWP or CWM, then using custom recovery to flash the latest CM12.x the best and only way to get from rooted Kitkat to rooted Lollipop?
4. I know there are some functional improvements in Lollipop but are they really that significant? I like the whole "material" thing which comes with Lollipop, but not at the price of loss of functionality.
Anyhow, here's my little sob story, which has a happy ending -- perhaps some of these details will elucidate my situation and lead to better answers:
I got tired of waiting around for Lollipop and had been unrooted by Kitkat for almost a year when I rooted again back in July 2015. I had wanted to go with the latest CyanogenMod Lollipop version, but ran into problems first using Heimdall (which refused to properly connect and write) and then trying Odin (against best advice post-root) to install a custom recovery (preferred TWRP but would go with CWM). Always led to that "unauthorized software" boot screen, which then necessitated reinstalling stock Kitkat and rerooting (I found the Ghettoroot .BAT file worked okay.) All was well, I was too busy to think about Lollipop but I woke up one morning about a month after I rooted Kitkat to find my Note II was stuck on red Verizon book splash-screen. Found a great article and YouTube showing all the keypress sequences which might exit a Note II from been stuck in boot -- but unfortunately not until after my further finagling just left me with a dead no-display-at-all device. I undertook Kobol's method, which requires partially reassembling the Note II's electronics outside its case and attempt to reboot with a very tiny screwdriver shorting a minute resistor on the motherboard right adjacent to the CPU -- I did in fact see the screen flash on briefly -- but I held my little screwdriver down too hard, accidentally gouged out the tiny resistor, and ended up buying a refurbished motherboard which very likely may have been scavenged from a stolen phone before going on sale on eBay. New motherboard worked great, I erased the original owner's info and data and proceeded to reinstall and root Kitkat. (Motherboard was already at I605VRUFND7) when I received it.
Anyhow, I also tried to install a custom recovery after I had new motherboard and rooted Kitkat. Using the TWRP Manager app put me back on the "unauthorized software" boot failure screen from Verizon, but I was able to Odin back Kitkat easily enough without losing my apps and configuration data. I believe I tried to use ROM Manager and Flashify as well -- but didn't find those apps very cooperative (though I didn't bother to upgrade to "pro" level on any of these in cast that matters). Unless I am mistaken, all these apps just place a zipped update file in the root of my internal SD card and then just hand it over to the Note II's stock recovery. I figured I just needed to stop and regroup later. That was a few weeks now.
Honestly, after the ordeal of having to replace a broken motherboard, and also -- after having looked at Verizon, Sprint and AT&T and the new Galaxy devices with no removable back and cracking the phone open necessary to replace the battery or upgrade the hidden microSD card and not liking that one would have to pay $600 over two years for a smartphone even further crippled at the cell carriers' requests -- it's even more important to me to be careful not to damage my Note II. (In fact, my Note II had turned out to be irreparable, I might even have even bought a refurbished unlocked Note 2 or 3 or 4 -- Samsung has made a real error on their latest generation of phones with their sealed backs and no user-accessible microSD reader.)
Yet, perhaps naively, I really do want to move on to Lollipop and even Marshmallow when CyanogenMod makes that available. So I really would appreciate it if you guys can verify whether what I intend to do (downgrading to pre-Kitkat in order to install custom recovery and then CM12.x) is workable? Or if there's a better solution? Or if I should just be content to have Kitkat rooted with all the fat cut off?
Many thanks. Hope my digression was not too long. Please don't anybody yell at me. XDA Developer's web forum is so full of very useful write-ups but unfortunately also some incorrect information and a lot of just plain useless posts -- it's really difficult sometimes to tell posts by guys who are actually experts from post by well-meaning folks with a lot of ideas but not so much expertise specific to SCH-I605 and VRUFND7. And I really need to get this right. (Granted that nobody on the forum can be held culpable should on mess up my phone based on their advice.)
Thanks once again!
I just recently damaged my new phone and my only option is to use one of my old phones. I just found out that 7 or 8 years ago I had rooted this phone and I am wanting to update the android firmware. I tried to update from the push notification but it does not work. I am thinking either the root or CWM is not letting it auto update.
I no longer need root and have been out of touch with the modding community for a long time. I am sure there is a simple way to do it. I just have no idea where to start. I just want a stock phone. I would appreciate some help thanks.
The phone is a Sprint galaxy S3 Model Number SPH-L710 Android Version 4.1.2