Related
What's up everyone, i'm new to the site and i was wondering if anyone would be willing to help me root my galaxy note 3. I've tried rooting in the past and failed terribly. I tried on a sprint gs3 and a verizon note 2, and i almost bricked both of them. So if someone with a lot of experience would help root my phone and install a custom rom, it would be greatly appreciated. As far as the type of rom, i could careless about appearance...i'm all about performance and battery life. So basically, i want a rom that "overclocks" my processor and removes bloatware and unnecessary apps. I'll take instructions on how to do it but i'd rather someone remotely control my pc [teamviewer] to help. I'll even paypal you like $5 for helping me. Thanks in advance!
I *would* help you, but I'm having issues rooting as well. I'm no where near new to it, been doing it since my HTC Fuze way back when. There are a couple of ways to root, Vroot, will pretty much root anything android and there is Kingo. I would give you links to both, but its not allowed, but you can do a quick google search and find them and info about them. If you're on the MJE build, I was successful with both methods, but I managed to cause a few issues when I was rooted with Kingo and had to Odin back to stock.
You need kingo 1.1.8 and safestrap. Both are one button operations. I rooted and had the safestrap installed and the modified twrp recovery in less than 3 minutes. Kingo 1.2 had a faulty script and causing errors.
Sent from my SM-N900V using XDA Premium HD app
czach5932 said:
You need kingo 1.1.8 and safestrap. Both are one button operations. I rooted and had the safestrap installed and the modified twrp recovery in less than 3 minutes. Kingo 1.2 had a faulty script and causing errors.
Sent from my SM-N900V using XDA Premium HD app
Click to expand...
Click to collapse
I rooted with kingo, it said successful. now what do I do? I don't know what to do with safestrap and all that other stuff. all I really want now is a ROM that will make my phone faster
JONES774337 said:
I rooted with kingo, it said successful. now what do I do? I don't know what to do with safestrap and all that other stuff. all I really want now is a ROM that will make my phone faster
Click to expand...
Click to collapse
Obviously since the bootloader is locked down tight, if you want a custom rom, you need to use safestrap.
You need to download safestrap apk file from hashcode's website, open it, grant root permission, and install recovery.
Once you install recovery you can reboot to recovery right from the safestrap app, then create and activate rom-slot-1
Once active, you can flash/install your ROM.zip file (I would recommend Hyperdrive or Jelly Beans) and reboot...that's pretty much it in a nutshell, its relatively easy
Needing some help with rooting as well. Instead of making a new thread I figured I'd hijack this one
I just tried to root with Kingo, it failed to root. I have a S3 SCH-I535. Where do I go from here to successfully root my phone? I used Kingo 1.2.0.1876. I could not find version 1.1.8.
Worldshaker said:
Needing some help with rooting as well. Instead of making a new thread I figured I'd hijack this one
I just tried to root with Kingo, it failed to root. I have a S3 SCH-I535. Where do I go from here to successfully root my phone? I used Kingo 1.2.0.1876. I could not find version 1.8.
Click to expand...
Click to collapse
Yo don't be hijacking my threads. Lol, jk. But if you google kingo and goto their website, you can hit their facebook page in the upper right corner. The facebook page has previous versions.
JONES774337 said:
Yo don't be hijacking my threads. Lol, jk. But if you google kingo and goto their website, you can hit their facebook page in the upper right corner. The facebook page has previous versions.
Click to expand...
Click to collapse
Thanks, finally got the download. All 1.1.8 links were leading to 1.2 download, had to use a mirror download to get 1.1.8.
Starting root now, hope it doesnt brick! Before I start...I guess I should ask, will rooting and going to a custom ROM fix my battery drain issues? Since the 4.3 update I get about 6 hours of battery life while not using my phone at except to turn the screen on for 10 sec to check the battery level.
Worldshaker said:
Thanks, finally got the download. All 1.1.8 links were leading to 1.2 download, had to use a mirror download to get 1.1.8.
Starting root now, hope it doesnt brick! Before I start...I guess I should ask, will rooting and going to a custom ROM fix my battery drain issues? Since the 4.3 update I get about 6 hours of battery life while not using my phone at except to turn the screen on for 10 sec to check the battery level.
Click to expand...
Click to collapse
If i had an answer to your question, i'd help you. But like i mentioned before, i'm new to the rooting process so you'll have to wait for an answer from these "experienced" fellas...
Well 1.1.8 failed as well. Get not supported error.
Worldshaker said:
Well 1.1.8 failed as well. Get not supported error.
Click to expand...
Click to collapse
I honestly don't know what to tell you. I have a note 3 and 1.1.8 worked for me.
Are you sure it's 1.1.8? I tried many times and downloaded 1.2even thoughit said1.1.8 and finally found 1.1.8 from a user on xda. If you need I can upload the correct version. But as previously stated you can find the most up to date safe strap on the note 3 board. Install the app press install recovery and every time your phone boots it will ask continue or recovery. Make a backup of stock and restore to any slot you want If you want to do stock rooted or select any slot and flash any rom (make sure it's for the Verizon note 3 because with a locked bootloader you cannot flash kernels) I'm currently running neon rom and with moderate usage I'm getting almost 3 days on a single charge. I find wifi downloading I can destroy 40 percent battery in about 2 hours though. Any other questions don't hesitate to ask.
Sent from my SM-N900V using XDA Premium HD app
Worldshaker said:
Well 1.1.8 failed as well. Get not supported error.
Click to expand...
Click to collapse
Most Likely downloaded the 1.2 version Like czach said.
look here v v v v
I have tried everything and I'm not having any success at all. I'm close to giving up unless someone has a better idea.
Sent from my SM-N900V using Tapatalk
You have to make sure you turn off antivirus. For me that meant turning off avg, Windows Defender and some other stuff I found it. Make sure you have developer options on USB debugging, screen stay on, and for some reason it seems like it helped to turn on unknown sources in your security settings on your phone. Sometimes it took me unplugging the USB and plugging it back in a few times in order for it to work but I just did it myself last week and making sure I did those things allowed me to do this pretty easily and reliably
Sent from my SM-N900V using xda app-developers app
Alright I will give that a try later tonight. Appreciate it.
Sent from my SM-N900V using Tapatalk
None of those methods worked.
Sent from my SM-N900V using XDA Premium 4 mobile app
I am on a Mac with a Windows 7 partition installed. Do you think this could be why it isn't working?
Sent from my SM-N900V using XDA Premium 4 mobile app
evoplug said:
I am on a Mac with a Windows 7 partition installed. Do you think this could be why it isn't working?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have yet to read that a virtual windows system works.
Sent from my SM-N900V using XDA Premium 4 mobile app
Ok I'm going to try using a friends windows laptop then.
Sent from my SM-N900V using XDA Premium 4 mobile app
Hello all
I recently upgraded from a sg2x I had it rooted and only had lbe privacy guard installed to manage pesky permissions and a few apps to trim the bloat ware.
My problem is that the s5 while it is s great phone has so much crap on it I literally have no idea where to start with trimming the fat. Just wondering if there are any ROMS availablethat do most of that for you? Pretty new to the whole scan and just thought I would ask. I would also be very interested to know if lbe privacy gaurd is still a viable permission limiting app. Sorry if I missed the answers in the forums somewhere but I have been having a hard time finding info specific to the Telus model of the S5 (SM-G900W8)
I have had the phone for one day and have had enough apps download on there own with very questionable permissions it has made me want to go back to the S2x and not bother with an upgrade. More insidious software on these things that enough. Any help would be much appreciated.
Cheers
I should also add that I have found the rooting guide but haven't done so yet as I am afraid of getting to crazy deleting bloat. I never used a rom just ran stock s2x and never updated it. Am curious to try something new in the form of a custom rom. I don't really use the phone for anything but music email and banking. Again any help would be greatly appreciated.
Sent from my SM-G900W8 using xda app-developers app
Hi, some galaxy s 5 g900f custom roms will work on the Telus galaxy s 5. I have the omega rom on my Telus phone. Uses the same recovery as well.
Sent from my SM-G900W8 using XDA Premium HD app
Right on thanks for the help. Did you find it got rid of most of the unwanted stuff? Much change in interface or anything?
Sent from my SM-G900W8 using xda app-developers app
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
REHolt218 said:
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I do not. I use a Miracast device
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Nice! Honestly haven't missed this feature much but glad we have fix now!
rkirmeier said:
Nice! Honestly haven't missed this feature much but glad we have fix now!
Click to expand...
Click to collapse
I do a lot of traveling and this is a great solution for watching movies, when it works. My WiDi device is fairly small and connects to the TV with HDMI. Since WiDi is a direct connect between divices and doesn't depend on the local wifi it works much better than Google ChromeCast.
I just wish I could get it to work again with my Samsung devices.
Sent from my SM-P900 using Tapatalk
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Wow so this is great news. One question is what effect if any will this have with root.
tonyz3 said:
Wow so this is great news. One question is what effect if any will this have with root.
Click to expand...
Click to collapse
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app
Duly.noted said:
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Flashed the stock recovery and miracast is working again. So this means we can't load up TWRP?
That is correct. If we can get support for mobile odin then it might be possible to quick swap between the two on the go. As it is I would reccomend making a backup in twrp then reflashing stock recovery. Then if you need to restore just plug up to odin and flash twrp again. They did mention that whatever it was should be fixable to work with twrp. So if they get a fix it should be easy to port over to ours.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?
ceomayl said:
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?
Click to expand...
Click to collapse
Root will not affect anything You already have installed
Sent from my SCH-I605 using XDA Premium 4 mobile app
Thx for the fix post. I am going to do it this weekend when i have sometime encase of an unforeseen issues.... But just so i am clear. I am rooted already and when i flash this will anything be lost-such as settings or any of the Xposed modules etc. If so, any suggestions on a backup method...
We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that
esgie said:
We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that
Click to expand...
Click to collapse
Sadly our device does not have the wfdengine.lib. None of the kitkat devices appear to. I do know from reading on the 2014 Forum that hdcp was the Culprit. Hopefully work can be done to twrp to allow its use without breaking this feature
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Please advise, I will have to convert the recovery.img file to a recovery.tar.md5 file in order to flash using odin, correct?
I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX
xdapao3 said:
I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX
Click to expand...
Click to collapse
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).
esgie said:
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).
Click to expand...
Click to collapse
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install
THEDEVIOUS1 said:
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install
Click to expand...
Click to collapse
Nice to know
Btw I replaced it after flashing TWRP, so it should work both ways.
Feel free to post it in the other devices' forums if you find it helpful.
esgie said:
Here's libwfds.so modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..),
Click to expand...
Click to collapse
Really thanks for being so helpful man, but there lies the problem, I can't get a Miracast setup and be at the constant risk that an update breaks it..
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
One has to ask, with tears in my blood shot eyes, why Samsung had to disable it in the first place.
Not a very friendly thing to do!
Chaos-sa said:
One has to ask, with tears in my blood shot eyes, why Samsung had to disable it in the first place.
Not a very friendly thing to do!
Click to expand...
Click to collapse
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
StNickZA said:
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
Click to expand...
Click to collapse
I read this post and quite frankly you have every reason to point out Samsung's short comings. They have got to big for there boots and when you have paid for a product, irrespective how much, you have a right to a certain level of expectations.
Lets face it we all want upgrades otherwise we wouldn't be here on XDA and for a product as new as the Note 10.1 2014 we have a right to expect 4.4. No they are not "legally" obliged to give it but hey our next buy will then become some manufacturer that steps up for us...the consumer. Sony is my bet!
Hehe. Oh well, with multi user accounts now working, I'm less worried about the Kitkat update than before.
Sent from my Nexus 5 using Tapatalk
I can confirm that this actually works!!!
StNickZA said:
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
Click to expand...
Click to collapse
I was one of those idiots haha, tbh its not unreasonable but everyone knows samsung are **** with updates and many things but Oh well you have found a solution so alls good.
Being a Samsung owner for over 2 years now I have learned Samsung are the worste for this but have just learned to accept it, its probably daft of me to expect others to accept it too.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.
Didnt work on my "NC2 Rom".
hanspampel said:
Didnt work on my "NC2 Rom".
Click to expand...
Click to collapse
Hmm, strange. I updated to P605ZSUBNC2 last night and repeated the same steps. All working just fine.
Hmm maybe its because i modified the secSettings.apk.
Edit: Ahh works now.
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
hanspampel said:
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
Click to expand...
Click to collapse
Thanks!! That's really awesome of you
Just a quick question - I imagine that there wouldn't be any issue with future updates right? When the option will be added officially I mean (obviously OTA won't work anyway though, with a 'customised system' preventing normal Samsung updates)
Thanx a mil
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
StNickZA...Thanx alot for this one line of code, added it last night and works PERFECT:laugh:
hanspampel said:
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
Click to expand...
Click to collapse
I've rooted my Galaxy Note 10.1 2014 edition (Original ROM), I installed the busybox, then I flashed the zip file, but nothing happened.
Please advise me.
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
While I can confirm this totally works like a charm, I am experiencing a weird issue. THE LOCKSCREEN
Its behaving strangely. When i change users (both pass protected) the lockscreen always keeps the previous user's wallpaper. Sometimes it also "freezes" for a couple of seconds and cannot enter pin or pattern.
Am I the only one having these issues?
Im just rooted with towelroot and supersu, fully stock
It works! SM-P600 4.3 in the UK whoop! many thanks!
Happy bunny, it's really saved the day, very poorly wife can now use it and I'll be able to hangout with her from our sons graduation (without me loosing all my work stuff)! Chuffed to bits!
I want to root my phone which I found towel route which I I downloaded but its not really working, which I found out is due to bootloader being locked. so I decided what I needed to do was unlock the bootloader but I'm reading all these forums which are talking about roms and I have no idea what that is. I was wondering if someone could kind of walk me through this a little bit like talk about it n smaller not so technical terms because I don't really understand it. I know some coding and a lot of the technical know-how but I've never really worked with phones and really deep programming I guess. I'm sure I could figure it out if someone explained it.
https://www.youtube.com/watch?v=NlK3r81kQPw&list=FLRvqjdmBGEGRU4qfddJMuDQ&index=33
Here's a video that might help a little. It's sort of old, but depending on which version of android you're on it'll probably help you get root access at the very least
What firmware version are you on? If you're on newer firmware the vid the other guy linked to is not going to work for you. There are tutorials in the general forum that can help you.
Sent from my Nexus 9 using XDA Free mobile app
Galaxy s4
I was able to root my phone using towel root, then I disabled Knox with supersu. I wanted to remove all the bloat wear so I thought getting a new rom would do it (I've been researching) and I tried that three times but it keeps resetting my phone to factory settings. What am I doing wrong? I tried CM and that pacman one. I really like the aok(whatever letter) one but it's not compatible with my phone. I have a galaxy s4 unlocked, it's at&t but I actually have tmobile. I have all the at&t software AND tmobile crud on here. I really want it gone. I was trying to install the roms through my sd card with my phone on odis mode.
plethoralaura said:
I was able to root my phone using towel root, then I disabled Knox with supersu. I wanted to remove all the bloat wear so I thought getting a new rom would do it (I've been researching) and I tried that three times but it keeps resetting my phone to factory settings. What am I doing wrong? I tried CM and that pacman one. I really like the aok(whatever letter) one but it's not compatible with my phone. I have a galaxy s4 unlocked, it's at&t but I actually have tmobile. I have all the at&t software AND tmobile crud on here. I really want it gone. I was trying to install the roms through my sd card with my phone on odis mode.
Click to expand...
Click to collapse
Are you using safestrap and flashing touch wiz based roms? Cm and Pac will not work on your device if you're using safestrap.
Sent from my Nexus 9 using XDA Free mobile app
Inever got around to downloading safestrap. I thought that was something you did after you downloaded the rom. And I've never heard of the other one. It shows up with something about verification problems. I should have written it down. It took so long for my phone to turn back on.
plethoralaura said:
Inever got around to downloading safestrap. I thought that was something you did after you downloaded the rom. And I've never heard of the other one. It shows up with something about verification problems. I should have written it down. It took so long for my phone to turn back on.
Click to expand...
Click to collapse
I'm not sure what firmware version your phone is on but I'm guessing it's on a newer version where cwm or twrp recoveries are not going to work. You'll need to install safestrap and install roms with it.
Sent from my Nexus 9 using XDA Free mobile app
Okay. I will try that. I did post a picture of my device information in my second post in case it had what you were asking get for.
plethoralaura said:
Okay. I will try that. I did post a picture of my device information in my second post in case it had what you were asking get for.
Click to expand...
Click to collapse
Sorry,I didn't see that. I'm on my mobile. You're on nc1 firmware. You definitely need safestrap.
Sent from my Nexus 5 using XDA Free mobile app