Related
Ok, this might be a MEGA noobish question, but i have never dealt with Android before so please bare with me XD
I have just (yesterday) got my Atrix on tmobile in the uk, an would like to root it to use Aura ROM to get the 2.3.4 features and general improvements it seems to bring, but is there any reason to wait any length of time?
Its my understanding that Android is completely OpenSource, so is rooting it voiding any warranty, or is it OK with carriers? I ask since tmobile offers a 14 day period to make sure im happy with the phone, and that it all works fine, which it seems to after my extensive playing/testing over the last 2 days, but if it does go wrong i wouldnt want to take it in, rooted, and have them say they cant help me.
any clearing up of this would be much appreciated!
You should wait until the return period is over before rooting it. This will give you time to make sure nothing is physically wrong with it. Rooting alone will not void your warranty. However, unlocking the boot loader will and you need to do that to load a custom recovery so that you can flash another ROM. An unlocked message will get displayed on the start up screen. Some carriers may not pay much attention to that when returning it. Motorola will most likely notice if you need to use the manufacturers warranty though.
Root will void your warranty, wait till the trial period is over just to be safe...
Sent from my MB860 using xda premium
i got my phone from AT&T and rooted it as soon as i got home, a week later i ended up hard bricking my phone and went into the AT&T store and got it replaced for free. now, i did also pay for insurance on my phone so if anything happened to it (even if it's my fault) i'd get it replaced, but it seemed as if the representative had no clue what he was talking about. i was honest with them and everything and told him i was trying to unlock the phone when it happened, and he just kind of smiled and nodded and then pulled out a new phone out of the back. i asked how much i owed him, and he told me nothing.
point of the story is, i wouldn't worry about rooting the phone. it's possible that you won't be able to get it replaced, but chances are the rep you talk to either won't know what rooting is, or won't care. unlocking your bootloader though, i'd definitely wait a little while.
thanks, that is a good point though that people in the shop probably wont understand/care about rooting etc.
Though your reply, Alcapone, has confused me slightly i thought rooting and unlocking the bootloader were one and the same, but apparently not. could you please explain what is different, and is there any reason for me to root without unlocking the bootloader?
basically for now, since im on tmobile who seem quite slow at updating, i just want to get a way to put gingerbread on the phone. im ok with waiting 2 weeks for roms, but 2.3.4 i could do with now, if its possible, can that be done just by rooting?
many thanks
ishamm said:
thanks, that is a good point though that people in the shop probably wont understand/care about rooting etc.
Though your reply, Alcapone, has confused me slightly i thought rooting and unlocking the bootloader were one and the same, but apparently not. could you please explain what is different, and is there any reason for me to root without unlocking the bootloader?
basically for now, since im on tmobile who seem quite slow at updating, i just want to get a way to put gingerbread on the phone. im ok with waiting 2 weeks for roms, but 2.3.4 i could do with now, if its possible, can that be done just by rooting?
many thanks
Click to expand...
Click to collapse
rooting your device is just giving it root access, so apps can access parts of the system that they normally couldn't. rooting is extremely easily, and reversible. there are multiple ways to do it, i would suggest either the one click root for all gingerbread devices here
or the preinstall method here
now, unlocking the bootloader is a lot different. it pretty much enables you to install custom firmware onto your device. you can install a custom recovery that allows you to install amazing ROMs such as CM7, Aura, Ninja, Alien, Red Pill, Homebase, etc. etc.
i'm still assuming you're on gingerbread, so unlocking your bootloader is a panicky process. you'll get a fake hard brick (0x1000 error), but all you have to do is boot into fastboot mode and type the command 'fastboot oem unlock'. you can find a really awesome script that will do it all for you here
now, unlocking the bootloader voids the warranty. it gives you a bit of text on your boot logo (the motorola screen) that says 'unlocked' and allows your carrier to know you voided the warranty. it's also irreversible, once unlocked always unlocked. so make your decision wisely
nevermind, just skimmed over your post again. my apologies, i misread a few parts originally, you'll need to unlock your device to install a custom ROM with gingerbread. you can unlock your device by flashing the .sbf files you can find in this thread here: http://forum.xda-developers.com/showthread.php?t=1136261
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
ishamm said:
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
Click to expand...
Click to collapse
After you get the bootloader unlocked and cwm recovery installed going back to factory settings is as easy as installing a stock ROM. Which is pretty damn easy
And rooting alone isn't enough to get you gingerbread.
Sent from my MB860 using xda premium
awesome, thanks again. one last question (for now at least ) before i dive in, is this all possible on a mac, i noticed a lot of the rooters (if thats the right word?) are .exe which worried me slightly, im away from my windows machine for 2 weeks now. if not i guess thats as good a reason as any to not void my warranty for now XD
ishamm said:
awesome, thanks again. one last question (for now at least ) before i dive in, is this all possible on a mac, i noticed a lot of the rooters (if thats the right word?) are .exe which worried me slightly, im away from my windows machine for 2 weeks now. if not i guess thats as good a reason as any to not void my warranty for now XD
Click to expand...
Click to collapse
You can go to the ihop thread in the dev forum and use the Mac sbf flasher provided there. After that use the sbf that corresponds to your device. Flashing the wrong sbf can brick your device so maker sure you get the right one. Then boot into fastboot and use the fastboot OEM unlock command.
You can root as well on a Mac i'm sure, I just wouldn't know how. I'm guessing the preinstall method I linked would work.
Sent from my MB860 using xda premium
ishamm said:
Ok, this might be a MEGA noobish question, but i have never dealt with Android before so please bare with me XD
I have just (yesterday) got my Atrix on tmobile in the uk, an would like to root it to use Aura ROM to get the 2.3.4 features and general improvements it seems to bring, but is there any reason to wait any length of t
Its my understanding that Android is completely OpenSource, so is rooting it voiding any warranty, or is it OK with carriers? I ask since tmobile offers a 14 day period to make sure im happy with the phone, and that it all works fine, which it seems to after my extensive playing/testing over the last 2 days, but if it does go wrong i wouldnt want to take it in, rooted, and have them say they cant help me.
any clearing up of this would be much appreciated!
Click to expand...
Click to collapse
if you know how to root id do so. i already rooted, and also bricked my atrix. flashing the 4.2 sbf unbricked it and rerooted no problems so far, just the benefits of root (using apps that can only work with root permissions, flashing custom roms) also why flash Aura and run 2.3.4 when you can flash honeyatrix and run honeycomb 3.1?
rob219 said:
if you know how to root id do so. i already rooted, and also bricked my atrix. flashing the 4.2 sbf unbricked it and rerooted no problems so far, just the benefits of root (using apps that can only work with root permissions, flashing custom roms) also why flash Aura and run 2.3.4 when you can flash honeyatrix and run honeycomb 3.1?
Click to expand...
Click to collapse
Honey atrix isn't really honeycomb. It's gingerbread with a bunch of mods installed to make it resemble honeycomb
Sent from my MB860 using xda premium
Alcapone263 said:
Honey atrix isn't really honeycomb. It's gingerbread with a bunch of mods installed to make it resemble honeycomb
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
oh ok been running it along time so why does my android version say 3.1 and not 2.3?
rob219 said:
oh ok been running it along time so why does my android version say 3.1 and not 2.3?
Click to expand...
Click to collapse
It uses some files from honeycomb that edits the version number. It's still gingerbread, trust me.
Sent from my MB860 using xda premium
Alcapone263 said:
It uses some files from honeycomb that edits the version number. It's still gingerbread, trust me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
i see well not gonna argue about it, just askin. still a great rom and very fast. i change alot of the look to my preference though. i may like the features and speed but im not a big honeycomb theme fan, i like my status bar white and such.
rob219 said:
i see well not gonna argue about it, just askin. still a great rom and very fast. i change alot of the look to my preference though. i may like the features and speed but im not a big honeycomb theme fan, i like my status bar white and such.
Click to expand...
Click to collapse
You should check out cm7. It's extremely customizable and really, really fast.
Sent from my MB860 using xda premium
Alcapone263 said:
You should check out cm7. It's extremely customizable and really, really fast.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
na not yet maybe after beta when everything works, kinda over cm now. new phone new roms hoping some new ones pop up here soon, but ill probly check out cm when its out of beta but most likely wont keep it as default.
after a bit of research it seems rooting on a mac is pretty tricky, since i dont have a vast ammount of terminal experience. is there a way i can forward some sort of app to the phone and root from the phone itself?
ishamm said:
thanks, so just to confirm, rooting alone wont allow me to update to 2.3.4? to be honest im not really to fussed about voiding warranty, it only lasts 2 weeks, and im away with no tmobile store even vaguely close for both of them plus i seem to be addicted to voiding the warranty on anything i buy by fiddling/overclocking asap, i cant help myself
i assume it is possible, if it does go wrong, to restore the phone to manufacturers settings and start again?
Click to expand...
Click to collapse
The 2 weeks is a return window with tmobile. Motorola, and most vendors, offer a one year manufacturer warranty. That is the warranty you void when unlocking the boot loader. Just wanted to clarify that bit.
ah thanks, i guess motorola WOULD notice its unlocked then. after some reading i think i'll use CM7, seems less likely to kill the phone, right?
the phone is insured, i guess it would be covered by that if i bricked it for good? if not i could take a hammer to it and claim it was a 'terrible accident' XD
I assume rooting the device will be quite easy, but what's Googles take on rooting?
Will it void the warranty and if something goes wrong (that isn't my fault) will getting it repaired by LG or Google be easy?
Sent from my One X
i have ever understand it... i have a nexus s, but all says that google's nexus are all rootable without lose nothing... but better wait who is more expert than me ^^
The easiest thing to do, is that if you have to send the device back to Google or LG, do a clockwork backup, put it on your PC, restore the phone back to complete stock and lock the bootloader. That way you are 100% sure it will be fixed without issues.
theoneofgod said:
The easiest thing to do, is that if you have to send the device back to Google or LG, do a clockwork backup, put it on your PC, restore the phone back to complete stock and lock the bootloader. That way you are 100% sure it will be fixed without issues.
Click to expand...
Click to collapse
I do that for my HTC one x at the moment but was always under the impression that they could tell if a device was rooted and then returned to stock state once again.
But if you say it's fine then i guess I nothing to worry about i suppose.
Thank you
Sent from my One X
enviii said:
I do that for my HTC one x at the moment but was always under the impression that they could tell if a device was rooted and then returned to stock state once again.
But if you say it's fine then i guess I nothing to worry about i suppose.
Thank you
Sent from my One X
Click to expand...
Click to collapse
I don't know about HTC or LG but I know Samsung put a flash counter on some of the phones which is a dead give away if you send it in for warranty work. From what I understand there is a way around the counter now and apparently you can reset it as well.
Sent from my ADR6300
riko540 said:
I don't know about HTC or LG but I know Samsung put a flash counter on some of the phones which is a dead give away if you send it in for warranty work. From what I understand there is a way around the counter now and apparently you can reset it as well.
Sent from my ADR6300
Click to expand...
Click to collapse
Motorola put something similar on the ATRIX 2 for counting root access.
Sent from my bootloader-locked MB865.
What disadvantages do I have by rooting? Had my n4 since friday
Sent from my Nexus 4 using Tapatalk 2
Have you unlocked the bootloader yet?
There are no disadvantages to root, think of it like having admin permission of your system.
Unlocking the bootloader will wipe your device, as a safety feature. On a nexus, since it's only one command to unlock, it's recommended to do that straight away if you even think you might start down the road to custom town in the future.
Sent from my Nexus 10 using xda premium
Yup...as far as I'm concerned, everyone should ALWAYS root. A - it's part of what's truly awesome about Android, B - it will more than likely come in handy at some point and C - there really isn't any reason NOT to do it.
Just do it soon after getting the device (I had my N4 for about 30 min before I started the process...within an hr of getting it, the bootloader was unlocked, it was rooted, had a custom kernel and it was ROMd) since, as stated, a wipe is usually required. And, even still, some know how with titanium can even soften that blow.
Disadvantages? Potentially void your warranty, less secure device (malicious apps that ask for SU permission), rom flashing addiction, spending too much time on XDA.
The occasional app won't run rooted - TWC TV, for example.
Sent from my Nexus 4 using xda premium
So what happens if I don't root right away? That's what makes me nervous
Sent from my Nexus 4 using Tapatalk 2
ridearoundsolo said:
So what happens if I don't root right away? That's what makes me nervous
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well, nothing. It's not a requirement.
You won't be able to use apps that need SU permission, that's all.
Unlocking your bootloader is not the same as rooting, you should do that asap if you plan on ever mucking around with your device.
lwfb said:
Well, nothing. It's not a requirement.
You won't be able to use apps that need SU permission, that's all.
Unlocking your bootloader is not the same as rooting, you should do that asap if you plan on ever mucking around with your device.
Click to expand...
Click to collapse
Why is required to unlock asap? I know about rooting its just the first time I've heard to unlock boot loader asap like does something get ruined if I hold off on unlocking the bootloader?
Sent from my Nexus 4 using Tapatalk 2
ridearoundsolo said:
Why is required to unlock asap? I know about rooting its just the first time I've heard to unlock boot loader asap like does something get ruined if I hold off on unlocking the bootloader?
Click to expand...
Click to collapse
It is not required to do it asap.
Some just recommend doing it quick because unlocking the bootloader wipes the phone. So you lose the data on there.
Story time:
Personally I always use the device for a while before I go near rooting and all the fun that comes with it, just to make sure I have a good product and stable device.
I had a Desire Z before, and had the motherboard replaced once because it had failed. When I got it back I tried it for maybe a day or two. I noticed it was a bit unstable and blamed it on the HTC software just being crap. So I rooted and flashed CM to it.
That turned out to be unstable as wel... Phone would just randomly reboot.
Unrooting and returning that Z to stock was a bit of a challenge. A guy on IRC helped me out tremendously and I'm still thankful for it, because together we succeeded.
And I could RMA once more...
So that's why I tend to wait a bit and confirm my device is solid before I go rooting.
stejoo said:
It is not required to do it asap.
Some just recommend doing it quick because unlocking the bootloader wipes the phone. So you lose the data on there.
Story time:
Personally I always use the device for a while before I go near rooting and all the fun that comes with it, just to make sure I have a good product and stable device.
I had a Desire Z before, and had the motherboard replaced once because it had failed. When I got it back I tried it for maybe a day or two. I noticed it was a bit unstable and blamed it on the HTC software just being crap. So I rooted and flashed CM to it.
That turned out to be unstable as wel... Phone would just randomly reboot.
Unrooting and returning that Z to stock was a bit of a challenge. A guy on IRC helped me out tremendously and I'm still thankful for it, because together we succeeded.
And I could RMA once more...
So that's why I tend to wait a bit and confirm my device is solid before I go rooting.
Click to expand...
Click to collapse
I agree about testing the device to see if it can hold on its own before rooting, my last phone the HTC one s was a nightmare with rooting and flashing, but I know this is much easier because I own a nexus 7 which is rooted and running codefirex
Sent from my Nexus 4 using Tapatalk 2
Hello I just receive my Nexus 4 and I Rooted 5 minutes later
Now I have a question If the Nexus 4 is Rooted it will continue receiving Android Os Updates directly from Google?
Thanks
Marioaguado said:
Hello I just receive my Nexus 4 and I Rooted 5 minutes later
Now I have a question If the Nexus 4 is Rooted it will continue receiving Android Os Updates directly from Google?
Thanks
Click to expand...
Click to collapse
Yes as long as it is stock and the kernel is stock you can receive OTA (over the air) updates. You might/will probably lose root though when the update is installed but that is not a problem, just reflash it.
Yea...you will possibly void the warranty. You can usually flash back to stock if need be and, if you break your screen or something and just want to use insurance or something, just dip it in water for an hr or so...they'll never know what you did to it other than dip it in water.
And yes, you do open the door to malware, possibly. Gotta be careful about what you install and what you grant permissions to.
The reason I say to do it soon, as was said, unlocking, (sometimes) rooting and romming will usually wipe your device. If you do all this as soon as you get the device, it doesn't matter. If you use the phone for however long, you'll lose all that data. That's the logic behind it.
I've had the phone for little over a month now and I just rooted it yesterday. I had no intention of rooting, but I got myself a Moga controller and to get the most out of that controller, it requires root.
Of course, by that time I already had all my apps & such configured exactly as I like them, so it was a bummer to have to re-download and reconfigure everything. ESPECIALLY the internal "sdcard"s contents. I was used to being able to restore and wipe without losing my personal files because all my prior phones had sdcard slots. It completely slipped my mind that the Nexus 4 "sdcard" is pretty much just its internal memory so I lost a handful of pics and other things. For these reasons, I would recommend that even if you thitnk you MIGHT want to root in the future, you might as well do it now and save yourself the time of further redownloading and reconfiguring everything a month from now.
This was a question I had so the responses have been interesting. I've rooted my previous non-Nexus devices (Mytouch 4G, HTC Sensation 4G) mostly so I could get an aosp like ROM. I had a Nexus One but never rooted it. Still trying to decide if I'm going to root my Nexus 4 because I haven't really experienced a ROM that comes without minor issues (Picasa, GPS/Navigation, etc.) The custom ROMs do have a lot of cool features though.
Sent from my Nexus 4 using xda app-developers app
The features and theming is tempting but I'm a bit worried if there's a performance drop, are there Roms that completely surpass stock speed and without bugs?
Sent from my Nexus 4 using Tapatalk 2
phon00b said:
I've had the phone for little over a month now and I just rooted it yesterday. I had no intention of rooting, but I got myself a Moga controller and to get the most out of that controller, it requires root.
Of course, by that time I already had all my apps & such configured exactly as I like them, so it was a bummer to have to re-download and reconfigure everything. ESPECIALLY the internal "sdcard"s contents. I was used to being able to restore and wipe without losing my personal files because all my prior phones had sdcard slots. It completely slipped my mind that the Nexus 4 "sdcard" is pretty much just its internal memory so I lost a handful of pics and other things. For these reasons, I would recommend that even if you thitnk you MIGHT want to root in the future, you might as well do it now and save yourself the time of further redownloading and reconfiguring everything a month from now.
Click to expand...
Click to collapse
Always backup your apps and data with Titanium Backup or with adb before unlocking your bootloader =/
ridearoundsolo said:
The features and theming is tempting but I'm a bit worried if there's a performance drop, are there Roms that completely surpass stock speed and without bugs?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If you're only worried about performance, CyanogenMod is as stable if not better than stock roms. If you're looking for optimization, I would suggest ParanoidAndroid. Most roms out there are pretty stable, except for a few hiccups, and I think the best advice is that you should try it personally and have a feel at it. :good:
I would say do it if you are interested constantly flashing ROMs. The only reason I've flashed my S2 because of the T-Mobile bloat. But then I messed more until I bricked.
The N4 is very clean and good as it is and I keep it that way.
I rooted my optimus s but all the roms for it sucksuck
Sent from my LS670 using xda app-developers app
So I ended up rooting and tried pa but am liking xylon stable a lot and about to give rasbean a try
Sent from my Nexus 4 using xda app-developers app
Hey guys,
I'm picking up my Note 3 on Tuesday. Gonna stay on the stock firmware out of the box, no OTAs will be allowed. Gonna root with Kingo. I dont wanna mess with recoveries or anything other than disabling software update to prevent kitkat from being pushed. I realize it could be an advantage however as I could then in the future use the 4.4.2 update as a type of recovery image, if I need to send it in for service or sell it. I know about sammobile and all other "offical" stock tars floating around but they arent really from Samsung. They dont even release recovery images for the dev edition! Kingo wont trip knox and I wont be modifying any system apps (I may even opt with using a permission denying app to block SDM from having network access, instead of freezing it, as it's less aggressive). I will make an ADB backup pre-root and restore it before updating as well.
If the time comes I could use Kingo or Superuser to unroot, wanam to fake the status as offical, adb restore and have the samsung experience store guys flash kitkat or use the OTA which, assuredly, would remove any and all traces of root. Sounds divine.
So will the update process, whether from the Samsung guys or OTA brick my phone if I do it? I should have everything removed by doing it this way. I don't like the idea of messing with all these different recovery tars as they arent 100% official. Just wanna make sure the Sammy update wont brick it, because it knows, somehow.
I'm in the same boat though worse off than you since I don't know how to do an adb backup. Sounds to me like Kitkat sucks and I just want to stay stock mje and block updates.
Sent from my SM-N900V using Tapatalk 2
There is nothing in the kitkat update that's essential. I know because I have it on my Nexus 10 and I wish I didn't. Rooted with SDM and bloat frozen. Will not update until they give me a really good reason to.
Sent from my SM-N900V using XDA Premium 4 mobile app
Yeah I agree with everything here. Kitkat totally sucks and I'm gonna stay on 4.3 for the duration of my phones life. But my question is, are we able, after rooting, to update officially to kitkat, be it an OTA or going to a samsung store and having them flash (without bricking it). I'm asking because I think it'd be a flawless way of reverting "back" (forward actually, from 4.3) to a genuine Samsung system after root. This would solve warranty worries or selling the device as rooted problems. The update would serve as a recovery image or the ultimate unrooting tool.
Just curious if it will brick the phone if done. If I need warranty service or to sell it, I dont want to go the sammobile odin route or any of the other "official" tars, because they're not 100% genuine. If we don't modify the stock rom and can use something like wanam to fake the sytem status and Knox isnt tripped, why would it not take the update perfectly? All this caution, an ADB pre-root restore and I'm pretty sure/hoping it would work wonderfully to get to a genuine samsung status, post root, for selling or service needs. Just need some clarification if it would actually work or bork the phone with an "unauthorize software detected" screen.
If kingo unroot works just unroot then accept the update no?
Sent from my SM-N900V using Tapatalk 2
recDNA said:
If kingo unroot works just unroot then accept the update no?
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
It'd be nice but from what I understand the update does some kind of checking to see how/what you modified. Kingo doesnt trip knox but any root with change the system status as "modified" instead of "official", which could interfere with updates. There is a well kown "unauthorized software detected" sign that comes up sometimes after update attempts. Not sure what triggers it though. Unrooting via Kingo doesnt nessisarily remove 100% of the root. This is what we'd use the KitKat update for, unless, it bricks it somehow because it's able to detect that you once rooted. But if you were cautious, didnt mod much, didnt mess with system files, did an adb restore and faked the system status with wanam, it's plausible to think you could accept an update afterwords without issues. But also, Im not sure if wanam will be able to fake the status after you unroot...
I don't want to take the update. I will disable the updater files once rooted. otherwise, i remain stock. when the time comes reenable updater files and immediately run kingo unroot. presto, all mods gone. now accept update. that wont work?
Sent from my DROID RAZR HD using Tapatalk 2
recDNA said:
I don't want to take the update. I will disable the updater files once rooted. otherwise, i remain stock. when the time comes reenable updater files and immediately run kingo unroot. presto, all mods gone. now accept update. that wont work?
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
This is what I'm trying to ascertain. I've read things that the unroot via kingo doesnt actually remove the binaries, it only unsinstalls superuser. There still might be some traces of it on there, and the update will see this and youll get this message after boot, post update: (a verizon induced soft brick for having a modified system before update)
http://www.s3forums.com/forum/attac...d-help-bad-uploadfromtaptalk1349867775446.jpg
Kingo even told me via their facebook when I asked about it, "There is a big chance that you cannot update your device via OTA. Rooting means you tampered your device. Even your KNOX stays un-triggered, you device status will turn from "official" to "custom". If you wanna back to the "official", you should use kies/Odin to flash back the stock ROM," which is not what I want, seeing as how the firmware from sammobile and others like it arent 100% genuine from Sammy. When you unroot, it will still say modified system, even if knox isnt tripped. The updates check this. You can use wanam to "fake system status" but if you unroot first, you lose wanam functionality and if you update when you're still rooted theres no way itll take.
Just trying to hash it out as it'd be the perfect way to restore to official stock, if need be. Not having the ability makes it pretty scary to do on a phone I paid $750 for. So we're between a rock and a kitkat. I really dont want that ****ty update either. But not having a sure fire way back, it sucks.
Does anybody know about using a samsung store to update from 4.3 to 4.4.2 after unrooting? I'm assuming they use Odin to flash and actually have the official firmwares. I'd feel better about going about it that way because so far I see a lot of warnings about OTA's (even after "unrooting"). Curious if that way would work without soft bricking your phone with the verizon warning.
Thanks for the 411. I also paid full price for my note 3 but I never intend to sell it. It will be a great wifi tablet. I'm always disappointed with value of smartphones after a year of use.
Sent from my SM-N900V using Tapatalk 2
recDNA said:
Thanks for the 411. I also paid full price for my note 3 but I never intend to sell it. It will be a great wifi tablet. I'm always disappointed with value of smartphones after a year of use.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
No problem. I don't worry so much about selling it, I can sell it on Swappa as they dont care about root. But for warranty purposes, it sucks. If something happens and we have to send it back and they find that it's been rooted or modified, they will not service it. It'd just be nice to have this card to play in order to get it back to a "trustworthy" genuine firmware. I'll insure mine though so yeah, spare wifi tablet I suppose. Just sucks the replacement will more than likely be refurbished.
Yeah, it's a great phone though. Are you gonna take any updates for it before rooting (not ****kat, obviously), or gonna root it out of the box (MJ9 software, I believe)? Just curious. I just don't trust Samsung's updates any more.
I never planned to root. I'm in mje latest update. I don't trust Kingo nor Vroot. That is why I never rooted. Kitkat sounds so horrible I feel compelled to root but I still don't trust available exploits. Like you said, a rock and a hard place... Just like a new NBA coach trying to make his bones yet score a good draft pick. LOL
Sent from my SM-N900V using Tapatalk 2
Getting a note 3 tomorrow.
Why does everybody hate the kitkat update so much?
Overproof said:
Getting a note 3 tomorrow.
Why does everybody hate the kitkat update so much?
Click to expand...
Click to collapse
Ruins easy access to SD card for one thing. S pen problems, some apps don't work etc.
Sent from my SM-N900V using Tapatalk 2
recDNA said:
Ruins easy access to SD card for one thing. S pen problems, some apps don't work etc.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
hahahahah!!! Stevens will be a great coach in a few years. Doc is a very very bad man. Hopefully we land Wiggins (or Parker). I'm on the fence about rooting too but from what I can tell Kingo is legit and worked for many people. the questiom is why dont they monitize it? thats scary to me.
So do you just deal with the software update popup by continually pressing home or back? if you defer it, after 4 times it installs on its own. same thing with rejecting it. I cant believe they don't give us control over our phones updstes (without rooting)! Hopefuly Verizon wont get it for a while.
There's a confirmed battery bug for kitkat ( on the nexus 5 atleast), the sd issue, a litany of instability, potentially, and the biggest deal with it: it breaks free wifi tethering and supposedly there will never be a way for developers to get arpund it. Yeah: I realllllyyy don't want that "update". If it aint broke...you know.
I don't know what I'll do yet. Sd card handling is an integral part of Kitkat and vzw won't improve it. Once the first announcement of imminent update occurs I will have to decide what to do.
I'm rooting for Celtics losses and I wish Ainje traded Rondo. I think we need a new team. I don't think Rondo will be a great influence on a young team.
Sent from my SM-N900V using Tapatalk 2
recDNA said:
I don't know what I'll do yet. Sd card handling is an integral part of Kitkat and vzw won't improve it. Once the first announcement of imminent update occurs I will have to decide what to do.
I'm rooting for Celtics losses and I wish Ainje traded Rondo. I think we need a new team. I don't think Rondo will be a great influence on a young team.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
HAhahahaha, I'm wiith you on all pages man. I would've stayed with my II but 4.3 is horrible on it and I'm really interested in the new Gear 2 watch which requires 4.3. Ironically 4.1.2 works like a BEAST on it but it wont support the gear 2. Samsung is fully turning into apple. If you do decide to root or find another way around the software updates, please let me know. I'll do the same for you. Kingo is one of the only ones that doesnt trip Knox but it's all but worthless if we cant get the system status back to "official" or get the kitkat update to install. Such a headache. Be careful with that software update popup, it's super consistent. Such a crazy way to have to use a flagship device. Most every time you press home, it pops back up. I found out that you can disable google services framework and that will prevent the update, but you also loose gmail, google play, you tube, maps and any other google app. Unbelievable.
There needs to be more NBA talk on XDA, lol. Danny has long since worn out his welcome. Still cant believe how he treated Pierce. I agree with the Rondo sentiment, wholeheartedly. His stock is falling as his athleticism fades as well. We need to blow up the team basically. I hope we resign AB, but I wont be shocked if he walks. We'll never get rid of Wallace's contract. Sully can be really good if he keeps healthy and developing. I used to love Green but now...I think we should deal him NOW. He clearly cant handle having the reigns and he takes way too many threes. Ironically enough Gerald Green is killing it for Phoenix right now?! Hoping for those ping pong balls too man. Hopefully we dont get screwed in the draft.
I'll keep you posted if I find anything.
Cheers--
Reilly1812 said:
There is nothing in the kitkat update that's essential. I know because I have it on my Nexus 10 and I wish I didn't. Rooted with SDM and bloat frozen. Will not update until they give me a really good reason to.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tablet and phone are 2 different things. Also each phone and tablet are not getting the exact kit kat. little things different but not the same action
Sent from my SM-N900V using Tapatalk
anthony92170 said:
tablet and phone are 2 different things. Also each phone and tablet are not getting the exact kit kat. little things different but not the same action
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
So you're not hesitant to update to kitkat on your note? If not, can I ask what features of enhancements in it make you wish to update to it? it is confirmed that sd write access for 3rd party apps and free wifi tethering apps have disabled, for some thats a big deal. If it's anything like other updates it has the potential to cripple the phones battery life and performance. 4.3 ruined my note 2 and the replacement 2 as well, losing around 2 hours of battery life on each. I'm hesitant to trust them again. With every update it seems things get worse, not better. and I cant see any huge features that would make me wanna jump from 4.3.
So, I've been at this Android thing for a very long time, and had unofficially retired from the XDA world when I bought a GS7 because I never thought rooting would even be possible. Well, now that I've rooted the phone and experimented with a custom ROM, I've come up with a question I don't know that I've ever had or read before.
I'm struggling with whether or not to stay in the rooted universe because I had come to take advantage of Samsung Pay quite often, and I didn't realize the battery difference would be what it is.
I want my phone rooted for two primary reasons, 1) to hack the provisioning so that I can use the native hotspot feature without needing a special app like FoxFi, and 2) to be able to remove all the crapware these phones come with.
So.. Theoretically here..... Shouldn't it be possible to root my phone, remove the crap, hack the provisioning, and then unroot the phone, revert back to the stock kernel, get my battery life back, and use Samsung Pay again? I never did load Samsung Pay on this phone since I've rooted it.
I saw psouza's unrooting guide but if I recall it was a destructive process..... I'd like to see if there's a way to root, set things up, then unroot and restore the phone to a state that maintains the hotspot hack and makes Samsung Pay happy.
http://forum.xda-developers.com/verizon-galaxy-s7/help/magisk-t3462583/post68962510
I had the same question. Apparently if you alter the system the stock boot image/kernal will not boot.
You will get a verity error.
bart77 said:
http://forum.xda-developers.com/verizon-galaxy-s7/help/magisk-t3462583/post68962510
I had the same question. Apparently if you alter the system the stock boot image/kernal will not boot.
You will get a verity error.
Click to expand...
Click to collapse
well poo....I wonder....since the S7 is still relatively new to hacking....I wonder if someone can figure out a workaround that would allow for tampering first, and a successful unrooting afterward. Or maybe this is a Android-wide problem...I've never really thought about this particular approach before....I've always just been always rooted, or never rooted.
I also have this hope that someone will figure out how to spoof whatever is necessary in order for Samsung Pay to still work.
I am using stang5.0liter's ROM and the only slight issue is the battery.......phone runs smoothly for me.....if Samsung Pay worked on this ROM I wouldn't even care about my initial question here.
spearoid said:
well poo....I wonder....since the S7 is still relatively new to hacking....I wonder if someone can figure out a workaround that would allow for tampering first, and a successful unrooting afterward. Or maybe this is a Android-wide problem...I've never really thought about this particular approach before....I've always just been always rooted, or never rooted.
I also have this hope that someone will figure out how to spoof whatever is necessary in order for Samsung Pay to still work.
I am using stang5.0liter's ROM and the only slight issue is the battery.......phone runs smoothly for me.....if Samsung Pay worked on this ROM I wouldn't even care about my initial question here.
Click to expand...
Click to collapse
It will not work. The original kernel for the device checks system verity. This is a part of locked boot loaders and android M+. If one bit of information is changed the original kernel will not boot. The reason we can root with the engineer kernel is it does not do this. Due to being in a "custom" status and non original kernel Samsung pay will not work nor will it ever work with this root method.
You have ruined my life with this response
So, why is the performance so bad on the engineering kernal?
spearoid said:
You have ruined my life with this response
Click to expand...
Click to collapse
Just the messenger lol. But honestly I can live without root. If I desperately needed root I wouldn't have bought a Samsung device as they are not the best for it. If you NEED root next time look more towards Nexus Phones, now Pixel and WAY over priced imo. Or research which phones have good root with an unlockable BL. For that I would stray from VZW branded devices and buy an unlocked version from the manufacturer that is compatible with VZW
bart77 said:
So, why is the performance so bad on the engineering kernal?
Click to expand...
Click to collapse
It was used for internal testing for Samsung. This was an early version of the first kernel they had for the S7, I believe and correct me if I am wrong anyone. It was fine tuned and then released but the engineering kernel was left in the dust.
Illogi.xbone said:
Just the messenger lol. But honestly I can live without root. If I desperately needed root I wouldn't have bought a Samsung device as they are not the best for it. If you NEED root next time look more towards Nexus Phones, now Pixel and WAY over priced imo. Or research which phones have good root with an unlockable BL. For that I would stray from VZW branded devices and buy an unlocked version from the manufacturer that is compatible with VZW
Click to expand...
Click to collapse
I don't need to have root. I bought this phone fully expecting to never be able to root it again. After several months of non root usage, it was very nice to enjoy some of the luxuries of a rooted phone again. I'm still torn as to which direction to go. I use the hotspot feature daily, and it works much better now than in the unrooted world for me at least.
I just wanted to see if there was any hope for having the best of both worlds.
spearoid said:
I don't need to have root. I bought this phone fully expecting to never be able to root it again. After several months of non root usage, it was very nice to enjoy some of the luxuries of a rooted phone again. I'm still torn as to which direction to go. I use the hotspot feature daily, and it works much better now than in the unrooted world for me at least.
I just wanted to see if there was any hope for having the best of both worlds.
Click to expand...
Click to collapse
I was too until the pokemon update lol then I decided no root.