Database Info

Will update still allow having root?

I got my wife the Samsung galaxy plus 7 for her birthday today and it's saying that there is an update for it. I'm not sure if its ok to except the update or not, because eventually I would like to get it rooted. Also, I read that in order to get root, you must first update the kies. Sorry for possible a simple question to some, but what are kies?
Thanks,
Sent from my AT100 using Tapatalk

bluezr1 said:
I got my wife the Samsung galaxy plus 7 for her birthday today and it's saying that there is an update for it. I'm not sure if its ok to except the update or not, because eventually I would like to get it rooted. Also, I read that in order to get root, you must first update the kies. Sorry for possible a simple question to some, but what are kies?
Thanks,
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
hey it is safer than safe to update it is infact encouraged to update at all times as updates are made to fix manufacturer bugs and/or issues that may be present on the device weather you have noticed them or not they will be present for sure like the SOD issue Screen of death a bug that makes your device shut down and/or reboot randomly with no control...this is a manufacturer bug and an update will be required to remove the issue from the device. so basically you will need to update on the device and with the Samsung kies (kies is a software that you will need to download from Samsung just search it on Google to learn more and to download kies is universal to all devices supplied by Samsung and i would also like to recommend not rooting your device until you are experienced enough to repair any damages you may encounter on the way if you do lol.
the purpose of root is to gain more advanced control of your device and/or install a custom ROM on the device (but we don't have any custom roms as of yet as Samsung will not release the sauce code) if you need any help and i will help you. if this post help you please press thanks button

jmar8124 said:
hey it is safer than safe to update it is infact encouraged to update at all times as updates are made to fix manufacturer bugs and/or issues that may be present on the device weather you have noticed them or not they will be present for sure like the SOD issue Screen of death a bug that makes your device shut down and/or reboot randomly with no control...this is a manufacturer bug and an update will be required to remove the issue from the device. so basically you will need to update on the device and with the Samsung kies (kies is a software that you will need to download from Samsung just search it on Google to learn more and to download kies is universal to all devices supplied by Samsung and i would also like to recommend not rooting your device until you are experienced enough to repair any damages you may encounter on the way if you do lol.
the purpose of root is to gain more advanced control of your device and/or install a custom ROM on the device (but we don't have any custom roms as of yet as Samsung will not release the sauce code) if you need any help and i will help you. if this post help you please press thanks button
Click to expand...
Click to collapse
I've rooted many devices and understand the consequences that comes with it. What I was wondering is, if I except the update will I loose the option of gaining root.
I had this happen to me before when the wife decided (I was still in bed) to accept the update to her evo. So while she had to sit back watching me change rom's, making backups, she was stuck running the stock os for a while. I do understand that at present there aren't any rom's, but I would still like to use TB, ad blocker and everything else that comes with having a rooted device.
Thanks for your reply,
Sent from my PC36100 using Tapatalk

The way that Garyd9 made the root script; by pushing it via recovery in a chroot environment; it should be safe to accept the updates. Unless Samsung changes the base recovery gary9d's method should always work.

bluezr1 said:
I've rooted many devices and understand the consequences that comes with it. What I was wondering is, if I except the update will I loose the option of gaining root.
I had this happen to me before when the wife decided (I was still in bed) to accept the update to her evo. So while she had to sit back watching me change rom's, making backups, she was stuck running the stock os for a while. I do understand that at present there aren't any rom's, but I would still like to use TB, ad blocker and everything else that comes with having a rooted device.
Thanks for your reply,
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
yes you can still get root i have the latest update by kies and i have rooted meany times on the device after messing it up LOL. i would recommend using the root and clock work mod combo its stated not stable but i have used it for moths and have backed up 100s of times and restored lol

[Q] JB Stock Needs Help

Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?

NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too

[Q] New owner. Typical Questions

I just want to ask some questions, seems like some of these threads are out of date.
My phone came out of box JB, so I need to restore down to ICS to root, then use a program called VooDoo to protect said root and update back to JB?
Unless my Bootloader is unlocked, What are the pro/cons of that, I heard you dont get OTA updates, but I could live without those, we can just download them ourselves right?

SirRudolph said:
I just want to ask some questions, seems like some of these threads are out of date.
My phone came out of box JB, so I need to restore down to ICS to root, then use a program called VooDoo to protect said root and update back to JB?
Unless my Bootloader is unlocked, What are the pro/cons of that, I heard you dont get OTA updates, but I could live without those, we can just download them ourselves right?
Click to expand...
Click to collapse
There have been a lot of misconceptions about unlocked bootloaders in this forum. Unlocking your bootloader doesn't necessarily mean the phone will not be eligible for updates, rather the updates will not install on a modified system. What is your real reason for root? Most people are always looking for the latest update, but mess up some files on their phone and don't have backup, in which case the update will fail.
With the Rogers/fido fiasco, we had people go back to the wrong Rogers version of software, since it was not posted properly on the Motorola firmware download website.
Another con is that your warranty would be totally void. Personally I haven't find the need yet to root this device and have had it for almost 4 months now!
Sent from my XT925 using Tapatalk 2

I wont agree for some people the modifications other people do seem trivial.
I've already rooted though, turns out I did have to do what I said above, now running 4.1.1 with Root
I root because a few applications I use, for instance SetCPU allows me to underclock the processors in my phone while the screen is locked, that saves a bit of battery life. I wish Motorola allowed a smart action trigger for when the phone screen was off though, this would help it even more so to save battery.
I use another app to change the lockscreen sounds, which requires root as well.
I havent looked at possible ROM's on this phone yet, as far as I know developers arent quite getting into this phone as deep as they usually do? Thusly I dont think i'll need to use a custom ROM. Just my own optimizations.

Rooting/Custom Rom-ing hesitation due to KNOX

Hello all,
I've searched all over XDA and Google, to give me definitive answer about issue i am about to raise, i rooted and put custom roms on all my previous samsung/htc devices, and WAS about to do the same for my Note 3 (its a beastly device, and doesnt need modifications, however it has been a routine for me to root and put custom roms into any devices that i've used)
Now the issue is this:
Yes, i've read about KNOX security system that Samsung has implemented, which would trip a counter and supposedly locked the bootloader of the phone, i've also read that due to the e-fuse that has been implemented, my Note 3 internals could be damaged due to it (?), and also i wouldnt be able to go back to the old version/bootloader as it will be parmanently locked by Samsung if i flash using Odin.
Do take note..that my Note 3 is not under warranty..so if KNOX triggers, it doesnt matter for me , as i wont be going to my local phone shop or official Samsung Officials (there isnt one here in my country) if anything would happen to my device. However i do need to know if its gonna mess with my device due to the e-fuse.
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:

qilrfn said:
My questions are these..
1) If i root it, using CF's method as i usually do..and will definately put Custom Rom in it...and that will trigger KNOX for sure..will it destroy the internals? say the MOBO..and the phone will be rendered useless and become an expensive paperweight (i dont have warranty, so no replacements)
2) If i use for e.g Omega Rom which released two versions, one, with 4.3 JB and one, with 4.4 KitKat...will i be able to go back and forth for e.g 4.4 to 4.3 as well as jumping to different custom roms with diffrent Android versions?! as i usually do with me previous devices
Thanks and i will definately delete this thread once i'm fully convinced that rooting , putting roms should be avoided or ''Since you dont care about tripping knox, go ahead and do it as ur previous devices'' kinda answer..
Truly Sorry if you guys come across this question already..i've searched for it and come to no avail.. this is my last resort. Thnks XDA and everyone.:good:
Click to expand...
Click to collapse
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)

I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.

radicalisto said:
Firstly wrong section - should go to Q&A
1) -- Well you can mess up if you don't follow the right methods (not hard)
2) you can only be on one, if you use 4.3 BL you can't use 4.4 and vice versa... once you go to 4.4 you cannot downgrade back to 4.3 unless you have an N900w8
Generally, rooting/custom ROM's won't hurt your device, just make sure you have the right ROM/Kernel and make the proper backups if needed.
Disable Reactivation Lock, and read about backing up your EFS and how to get out of it if it goes mad (which it sometimes does at random)
Click to expand...
Click to collapse
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)

ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)

qilrfn said:
Thanks for answering first of all..will defo hit the thnx button..
for the 1) i always make sure i read the instructions and follow steps..no problem there..
2) this one tho..is a bit weird for me..i was able to do it on my note 2..going back and forth 4.3 to 4.1.2 cus i found the 4.1.2 more stable..i guess for note 3 i cant do that anymore? even if use custom roms to up/downgrade?
thnx for ur time..and will take ur advice next time on posting it at the q and a section (still learning)
Click to expand...
Click to collapse
since note 3 came with 4.3 and currently latest stock is 4.4.2. even if u wanna go back to 4.3 from what i read around it is not possible. There are alot of aosp roms and stock rooted roms with all kinds of kernel build for both stock and aosp. Im sure if u were to follow the instructions given and do it diligently surely nthg goes wrong unless u overclock ur phone too high or flashing stuff which weren't meant for ur specific device then nthg to be afraid of. I sure glad i went ahead and root. Coz to me knox is a totally BS. all down to ur own preference. u like it u root it u use it. best is to keep reading different threads.
Sent from my SM-N9005 using XDA Premium 4 mobile app

radicalisto said:
ON 4.3 you once you go to MJ7 Bootloader you cannot downgrade -- however you can go to ML and MK bootloaders and go back to MJ7 again.
For some reason Samsung blocked a downgrade to 4.3 from 4.4 (as the Note shipped with 4.3 no logical reason to allow 4.2 imo) - but if you choose to move to 4.4. bootloader do be aware it can be buggy on some devices (NEE region also Hong Kong notes have issues) - If you have a read around you will see the issues people are having and not having with stock 4.4.
There's plenty of ROMs for both bootloaders CM works on both and most of the Stock based ROM dev's have moved up to the newest NB* Bootloader from NA* - I flashed 4.4 day it leaked (the next hour to be precise and I have had no issues)
Click to expand...
Click to collapse
Okay..so i would only flash 4.4 roms when Im really really convinced that its time for KitKat..but as of right now, i can only play around with 4.3 roms..ok..understood. You've cleared my doubts man, thanks a bunch and i guess its time to root and flash.

pete4k said:
I think Radicalisto didn't make it clear enough: I'm not aware of tripped Knox flag affecting anything else on the phone except for warranty and inability to use Knox software. Any type of phone issues would probably be due to user error, or loaded software, not the flag itself.
Click to expand...
Click to collapse
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.

qilrfn said:
I did read somewhere, the e-fuse is like an internal bomb..if i flag it, some sort of ''internal parts destroyer'' would be unleashed and mess up my device. I guess its just a rumour...hopefully.
Click to expand...
Click to collapse
If it's not humour, there's gonna be a lot of angry Note owners here on XDA -- Some tripped KNOX accidently lol - I wouldn't worry too much in all honesty.

I'm sure using cf root trips knox
Sent from my SM-N9005 using xda app-developers app

An e-fuse is just a silicon bridge on the processor that gets burnt out. Once you burn the bridge it can't revert back.
This is technically damaging the internal hardware BUT this is due to Samsung software doing this so I don't see how they can claim we have damaged the hardware.... There should be no other problems resulting from this....

First of all, many people already claim their phones had Knox flag reset to zero by Samsung service centers. Either they're all lying (why?), there are more than one e-fuse inside and Samsung can simply reset software to ignore burned fuse and check next one, or the whole e-fuse story is made up and not true. Personally I lean towards the last possibility, for 2 reasons: e-fuse is permanent so couldn't be reset and if they're using multiple e-fuses then it is not more secure than encrypted software code and also possibly e-fuse could be defeated from tripping: I believe e-fuse needs higher than normal voltage to be burned out (otherwise it could burn accidentally) and that voltage is probably coming on separate rail, I wonder what would happen if one would either cut this high voltage or short it out, just during flag tripping operations.
Secondly many people tripped their Knox flags already, if there was some side effects, we would know about it already.

2PZC5

Just got this device so I'm extremely new to this, and while I'm aware of the rooting process and etc, I was wondering if my model can support flashing full on AOSP roms like Lineage or Slim?
I'm not 100% sure, seeing as how there's an entire Sprint section for roms, however I've seen 2PZC5 users report here:
https://forum.xda-developers.com/u11/development/rom-slim7-t3656985
using the rom just fine, so I'm kind of confused.
Any clarification would be appreciated!

No signal on sprint/Verizon/dualsim and inconsistent on usa wwe.

shivadow said:
No signal on sprint/Verizon/dualsim and inconsistent on usa wwe.
Click to expand...
Click to collapse
So I should avoid AOSP roms and stick to stock roms/sprint roms?

For now, yes.

shivadow said:
For now, yes.
Click to expand...
Click to collapse
Alright, thanks for clarifying.
A few more thing I'd like to clarify:
I've been looking into the open nature of this device, and I was wondering a few things:
I've looked into S-OFF, does it at all heavily affect casual use of the device (as in ROM flashing, rooting, etc?) or does it only affect developers?
If S-OFF is important, in the future will it be mandatory to get that $25 tool in order to achieve utilizing anything on the device?
You mentioned "For now", does that mean to suggest that the Sprint variant/sprint modem/network will eventually be universally compatible with every other rom for this device or is it dependent on what sprint/HTC releases for that specific variant?

S-on is a security flag to lock the system partition from any permanent changes. So if you were to copy a file to the root of the phone it might take but after a reboot the change will be gone as if it were never done. To prevent the changes from resetting you need s-off to remove the security flag so the system partition becomes writable and changes are kept.
S-off is not developer orientated as developers develop on pc's and laptops then port it to the needed format. S-off is more about circumventing security that the manufacturer put there to stop you bricking it from doing silly things to it like flashing untested firmware and using said firmware to facilitate theft. It's long winded and quite political.
So to cut a long story short, s-off is needed if you want to change any part of the firmware that is loaded onto the device permanently.
As my own personal opinion, should you wish to mess with firmwares, even though s-off is not absolutely necessary to flash custom roms, s-off is essential as it opens up more options to a recoverable device BUT it is a double edged sword. You can also permanently brick your phone should you not know what you're messing with.
As for AOSP, it is a new concept for the U11 so it will have issues. The issues will be ironed out over time with the most critical issues being addressed first. You might find that in a week it is fully functional as a daily rom but in turn you might not, it may take weeks. But it will be done!. It depends on how important the devs see it.
The modem etc is the firmware, not the rom. If you change rom it wont change firmware, in fact the rom has to be compatible with the firmware it will go on to.
Just keep your eye on the progress and see if it changes. For now the rom runs but no cell signal to sprint or verizon with choppy signal on the unlocked us variant.