In addition to enabling ADB, SuperNooter will also mount the NC /system partition and copy over Superuser.apk and the su binary. This means you do not need z4root! You should see Superuser in your Extras/App Drawer after booting from the SD card.
Tested with WinImage under Windows and dd under Ubuntu.
http://muffinworld.net/android/nookcolor/supernooter0.1.zip
Thanks for making things even easier!
-CC
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Novarider said:
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Click to expand...
Click to collapse
Yup...do exactly what you did with nooker only use this image. Same steps.
Ok but do we need to wipe anything if we already used nooter? I don't want to brick my NC. Who is going to be the first to try it out? I would but I don't know anything about programing so if I messed it up I would be screwed
You can use supernooter on top of an existing nooter to gain Superuser. I would not try it if you already have Superuser (why would anyone?).
Mistar Muffin...you are the man!!!!
Just picked up a NC today and have been prepping for the past couple days...and pleasantly surprised that the steps have diminished with this.
Thank you!!!
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
johnopsec said:
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
Click to expand...
Click to collapse
What tone? I didn't say a single bad thing about the guy. I just dont want to brick my NC since im not a programmer and probably dont have the skill to fix it if something went wrong
Mistar Muffin said:
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with. The other thread you started has people in it that are getting "bricked" devices. I didn't know you didn't write the particular program that was causing this. I was not implying you were doing anything wrong I just don't want a "bricked" device.
Novarider said:
What tone? I didn't say a single bad thing about the guy.
Click to expand...
Click to collapse
Novarider said:
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with.
Click to expand...
Click to collapse
Novarider, I think that it's just the frustration of people coming on the forum and making posts with big bold red letters that say "YOU BRICKED MY NC!!!" and the like... As many others (including myself) have already stated, it's very difficult to brick a NC. I've yet to do it and I've done some VERY off-the-wall stuff with mine. My personal frustration comes from those two things.
So, sorry if you felt wrongly persecuted by my post. It wasn't directed only at you but at others who have screamed, yelled and lamented about one thing or another "bricking" their NC.
Friends?
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
What are talking about "bricking" devices? Have yet to see anyone claim to have "bricked" a Nookcolor...
That being said, don't think it's possible to brick one with current set of tools..
-CC
Novarider said:
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Click to expand...
Click to collapse
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
norkoastal said:
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
Click to expand...
Click to collapse
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Novarider said:
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Click to expand...
Click to collapse
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
johnopsec said:
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
Click to expand...
Click to collapse
If you figure out an easy way to install the keyboard without having to rename files in system or anything like that please let me know. I hate the stock keyboard on the NC
Step-by-Step Needed
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
docfreed said:
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
Click to expand...
Click to collapse
It would be great if this activated it because I can't install apks from the sd card now
Related
I used to work with WM 5 & 6 phones, had plenty of them and enjoyed them all until I discovered the HTC Magic. What a giant leap forward!! Especially when using Google Apps as we do. I am however a bit reluctant to root the magic as it doesn’t seem like a walk in the park. I really miss being able to backup SMS messages and all the other apps that only run on rooted devices.
So my question is if the HERO is a rooted device or not.
Does anybody have an answer to this question? I’m so tempted to preorder one
the answer to the question should be probably yes seing how people have the system dump files. so its just a matter of time
In the meantime, you can back up SMS and MMS with GBackup from Market - backs up to Gmail automatically - can also back up call log and pics...
Dayzz
Apologies for my ignorance but what does rooting the phone mean? I've just come from using a Windows mobile phone - which I have been using since the original SPV!
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Ofcourse it's not 'rooted' when you unpack it from the box.
Eventually I'll guess the Hero will be rooted, but when and how... we'll just have to wait.
dipje said:
Ofcourse it's not 'rooted' when you unpack it from the box.
Click to expand...
Click to collapse
Easy son... He asked, I provided.
barryallott said:
Easy son... He asked, I provided.
Click to expand...
Click to collapse
wasn't ment to be offensive in any way ...
barryallott said:
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Click to expand...
Click to collapse
But as in Unix /Linux you use an ordinary login for normal day to operations and su to to use root. You have to consciously change your privelidges which is safer!!
Simon
Lots of useful info on allsorts, including rooting and other hacks here
http://forum.xda-developers.com/showthread.php?t=542452
Daisy xx
***UPDATE***
I am removing this tutorial from general public view. if you read the warnings/disclaimers and are still interested you will need to read the links below and go about it yourself.
--------------------------------------------------------------------------------------
first off credit for this idea go to all the people/sites linked below. IF credit is missing where due please notify me and i will resolve. This is just a gathering of other posts and steps that worked for me.
This will wipe your device. backup anything and everything before proceeding.
If you are not willing to take it upon yourself to research any problems that arrise and fix them yourself DO NOT ATTEMPT.
If you are unwilling to wipe your stock Firmware DO NOT ATTEMPT.
If you are unwilling to start with a fresh nookie color SDcard NO NOT ATTEMPT.
If you are unable to fix your problems or want to revert to stock you can do so following the link at the bottom of the page
This is for advanced users. Make sure you read and reread everything before attempting anything! I take no responsibility and offer no promise of support if you make yourself a $250 B&N brand paperweight. keep in mind the nc is hard to brick (know from experience) but anything can happen, so be warned and proceed with caution.
if something below is not clear visit the links provided and look for your answers there. they are there and the more you read and learn the more sense this will make. if you are still unable to find help post here and i will try to get you going.
now on to the good stuff. I just wanted to gather the various posts and links that i used to gt a fully working froyo running on my nc from the internal memory (emmc) and present them in a step by step guide for others wanting to run NF from their internal memory and have no need for B&N stock. Flash is working if you install the proper apk. this is not installed out of the box. After installing to your EMMC you will be able to use any sdcard as you normally would in android. I am using a 16gb card with no problems.
***steps removed... see top of post***
helpful links:
http://forum.xda-developers.com/showpost.php?p=10254900&postcount=138
http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
nookdevs steps for creating nookie froyo sdcard:
http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
nookie froyo thread:
http://forum.xda-developers.com/showthread.php?t=883175
nookdevs nookie froyo tips:
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips
wipe nc to stock: (download the images and run the commands from an adb shell.)
http://forum.xda-developers.com/showthread.php?t=919353
Flash back to clean stock ROM (nook devs) http://nookdevs.com/Flash_back_to_clean_stock_ROM
1. first you will want a fresh NF sd card. I tried to use my seasoned nf card and ended with a brick... if you have google apps installed you will not be able to get past the android screen and will have to reimage as stated above. create your fresh nf sdcard following the steps at nookdevs here
Click to expand...
Click to collapse
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
samuelhalff said:
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
Click to expand...
Click to collapse
I tried the touching four corners. no go. several roms required that back when i was using a D1... I couldnt for the life of me figure it out so just scrapped and started from scratch.
thanks for your input. i planned to clean this up a bit, was just in a rush writing the original. Thanks again for your help. couldnt have gotten this far without your steps to start off.
Eager to try this out ... but will it be able to see a non-NF SD card I enter in? Will it recognize it, and let me see it as mass storage when the Nook is plugged into my PC?
Very well written, just copy and paste the code into the console for the most part ... Runs nice and fast, I have a few FC's to clean up but that is due to me not factory resetting the NC prior to doing this as I am an impatient person! I must say it is very nice not to have the B&N notification bar at the bottom of the screen.
So if this is really 2.2, does it have flash?
theyownus said:
I used 0.5.9 and replaced the vold file with the one from 0.5.8 making sure to maintain executable permissions.
Click to expand...
Click to collapse
a) What vold file? Searching for "0.5.8 vold" on this board produces no hits.
b) Executable permissions on what? This "vold" file or something else?
Don't want to be "that guy" but date should read 1/20/2011.
Thanks gonna give this a shot.
What happens to the Media partition?
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
starkruzr said:
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
Click to expand...
Click to collapse
Re-run ADB configuration. Make sure id is 0x2080.
How do we fix the SD card error. I am unable to do anything with the SD card.
samuelhalff said:
Re-run ADB configuration. Make sure id is 0x2080.
Click to expand...
Click to collapse
Wow. This is INSANELY important and this is the first time I've ever seen mention of it. Every other post simply assumes your ADB "just works." I have been endlessly frustrated by the lack of working ADB on this thing such that every time I do something with my NC I have to find a way to first install ADBWireless.
http://fineoils.blogspot.com/2010/11/pokey9000-has-got-self-booting-image.html
The instructions to get it working are in here, folks. Can these instructions be put in a sticky somewhere? This is about the least-obvious thing I can think of.
Is there any improvement in speed and reliability running this from the emmc as opposed to a class 6 uSD?
"extract them to their respective folders"
Nothin but bootloop
theyownus said:
first off credit for this idea go to samuelhalff
links:
original steps from samuelhalff http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
Click to expand...
Click to collapse
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
[Replace the files in /system]
It would also be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
fattire said:
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
Somewhere in there it would be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
Click to expand...
Click to collapse
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most of the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
Please know that my original post recomanded doing dd's of all partition. That way reverting back to stock was easy. My post also mentionned emptying data.....
What do mean steps aren't that different?
Sent from my HTC Desire using XDA App
samuelhalff said:
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
What do mean steps aren't that different?
Click to expand...
Click to collapse
Ah, I just mean it's all the same idea-- out with the old, in with the new. Nothing particularly genius about it. In any event, it's not really a matter of credit. We all stand on the shoulders of giants. I was just amused is all... so let's just have fun, eat, drink, be merry, and dance in the rain.
It may turnout that English isn't the OP's native language. Although it isn't mine either..
Nothing really seems genius once you get to understanding it.. but as a newcomer, I still had a bit of trouble getting the sdcard to mount..
Sent from my HTC Desire using XDA App
So I've been doing this android flashing business a long time
And I've got a real mess on my hands. I'll be ****ing with this for the rest of the night! Thanks!
MOD EDIT : As requested by OP, I'm closing this thread.
Everyone can continue the rooting related discussions on the other thread linked here. Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!].
All,
Here is a "one click" script to root your Nook Tablet AND install gapps (Market) all in one shot. It also includes the latest superuser binary and apk (automatically installed). MAD PROPS to Indirect for being the first to get root on the NT. This script builds off of his (and others) work to make it a bit easier.
I need people to test this. That being said, RUN THIS AT YOUR OWN RISK. It may work perfectly, or it may explode your Nook. You've been warned!
1. Download and extract the zip file located at https://rapidshare.com/files/3156164791/NT-One-Click-Root-by-anlog.zip (PLEASE MIRROR THE FILE FOR ME SO YOU DON'T KILL MY DROPBOX ACCOUNT).
2. Factory reset your Nook Tablet (just do it).
3. Run Windows 7 (32-bit or 64-bit). Sorry Mac and Linux, but that's not my arena.
4. Enable USB debugging and sideloading on your Nook (download an APK and try to install it with package manager. Hit settings and set the options). YOU MUST uncheck "auto mount USB" or debugging won't activate. There are also two checkboxes for debugging and staying awake - make sure both are set. DO NOT REBOOT your Nook once you enable these settings.
5. Plug in your Nook and point Windows to search for the drivers in the usb_drivers directory from the etracted file. The driver has been modified to work with the Nook Tablet and you don't need to mess with any adb.ini stuff. It's ready to go.
6. Once the driver loads, make sure you have a device called "ADB Composite Device" (or something similar) in Device Manager. As long as you don't have an item called "Nook Tablet" with an exclamation point, you're good. Once you are plugged in, check the status bar on your Nook and make sure USB debugging is enabled (there will be a little robot indicator).
7. This step is optional, since it is run at the beginning of the script, but you can open a command prompt AS ADMINISTRATOR and go to the folder where you extracted your files and run "adb devices". It should list your Nook serial number. If it doesn't, start over.
8. Run a command prompt as Administrator and then run the NookTabRoot.bat file to root your tablet and install gapps. Your tablet will automatically restart once the script finishes.
This script is ALPHA and probably won't work, but that's why I need people to test. If anyone finds a way to make it better, please feel free to modify it (as long as you credit me and Indirect).
Good luck!
MIRROR 1 - http://dl.dropbox.com/u/7364988/NT-One-Click-Root-by-anlog.zip
Thanks a lot, this is going to be quite helpful.
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Indirect said:
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Click to expand...
Click to collapse
Your root method is not easy enough for the average user, which is why I've posted this.
I'm not removing anything. It's up to the community to decide if they want to try my script or not. I will host it and setup my own mirrors if I have to.
conundrum768 said:
Thanks a lot, this is going to be quite helpful.
[Mirror removed in light of Indirect's post below]
Click to expand...
Click to collapse
Sorry to see you cave in so easily...
I'm not being disrespectful but my script really isn't too complicated. I was working on rewriting the thread anyway I just haven't gotten the time yet until now. I've been out all day.
This early in the process, it is great having multiple ways to achieve root.
Can't you each add a disclaimer in your package "If you use this method to root, don't use any other method without doing a full factory reset first" or whatever words would be appropriate?
Mostly - don't get ticked at each other.
It's not a multiple way, it's verbatim my script with his added to it.
This is not a glory or recognition thing. This is something that I think will greatly help the community of average users with little to no experience with things like ADB or Unix commands.
Many every day users are discovering XDA and it can be very difficult for them to navigate through the forums and find what they are looking for. My goal is to make it really easy.
The script will not blow up your Nook. The worst thing that can happen is that it just doesn't work.
Not sure what else to say, but this "only one user is allowed to help people root" nonsense doesn't work for me, nor the rest of the community. Sorry Indirect. If it helps, I've credited you at the beginning of my script.
OK - then I would say don't include an early version of a root script except by reference... Let the original author handle the bugs and enhancements.
I dont see a problem with useing each others method as long as the appropriate credit is given when you use someone else's work in your own.
Indirect said:
It's not a multiple way, it's verbatim my script with his added to it.
Click to expand...
Click to collapse
You mean your script with a bunch of STANDARD adb commands in it? Not exactly rocket science. Did you write zergrush? No, but you used it (and credited them accordingly).
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Indirect said:
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Click to expand...
Click to collapse
YOUR SCRIPT IS A BUNCH OF STANDARD ADB COMMANDS. That means that 100% of all other ADB scripts out there use elements from the script you pieced together from other scripts.
Get over it. You obivously only care about recognition. My only goal is to help other people.
anlog, you have clearly not seen any of my other work. I'm not in it for recognition, I need to know if something goes wrong at all and if so, what caused it. That's it.
Indirect said:
I'm not in it for recognition
Click to expand...
Click to collapse
Then stop telling people to remove their work and instead write a better/faster/easier version.
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
okay, so not to get in the middle of anything, I will say I've successfully rooted my nook tablet with the original method. didn't have any luck installing the android market (and getting it running).
as such, I've done a factory restore and have downloaded the script here.
as someone who is fairly computer literate, but is VERY new to rooting (short of 1 click root), I will take the shortest path possible. no loss of credit to indirect. please guys, all your work is recognized.
will report back shortly.
Indirect said:
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
Click to expand...
Click to collapse
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
anlog said:
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
Click to expand...
Click to collapse
Sorry for getting annoyed and worked up but I already had to play "Dueling Batch Scripts" in the evo shift section when mine was CLEARLY superior to the other ones by far because I was still developing it. :| So again, my apologies for losing my head but don't wait too long for my REAL script to be thrown together sometime tonight and blow yours out of the water.
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
First off, before I get into it; nay sayers and trolls please keep the thread clear. Hopefully we can figure something and more minds together normally equal victory.
Last night an idea hit me, I use a hack with Windows that allows admin permissions and I don't have enough info about android apks to say that it wont work.
In Windows (yes I know they are way different) if you can figure a way to temp change one sys program to be command prompt, you can add users, change admin passwords, delete logs and the such. Basically you own the box at that point. Im not going to go into the details cause as far as I know M $ hasnt fixed it and I dont want them to.
So if we can find an apk with root writing permissions and can change it to be a term emulator we should be able to chmod root.
I have made some attempts, using the hidden menu apk. I figure it can change the prop file it should have root privileges; with no luck. Maybe I am not repackaging the apk correctly or something?
If someone that knows more about apks thinks it may be a possibility lets get to cooking!
The Command Prompt trick you're talking about is very well known. It's been around since Vista and has yet to be patched and unlikely to be due to the nature of how it works.
Thanks Pirate, I know what versions it works with. But I guess no one knows how we can possibly accomplish the same in android.
Zer0C0oL said:
Thanks Pirate, I know what versions it works with. But I guess no one knows how we can possibly accomplish the same in android.
Click to expand...
Click to collapse
If you did, wouldn't you end up in a bootloop due to dm-verity, or is this not modifying /system?
Lifehags said:
If you did, wouldn't you end up in a bootloop due to dm-verity, or is this not modifying /system?
Click to expand...
Click to collapse
The way I understand the DMVerity mechanism is it rebuilds its trust chain every time a legitimate system change is made. When you perform a PRL update, the app makes a change to the system. This does not equal bootloops and I believe we can accomplish the same via this hack, if apk permissions can be loaned.
In the M$ hack you can't leave the change in place as it messes up other processes. Basically you use it to add a user with admin permissions/ open a backdoor and then cover your tracks: which one step is reverting the swap so there are no system issues for the users to find.
Alas, I fear the people this post should be reaching are the ones working towards claiming the bounty and for that reason collaboration will be non-existent.
@Zer0C0oL, please note that unless you are a developer working on a recovery, ROM or a Kernel, you should not be posting the development section. Please refer to this announcement if you have any questions.
I've moved this thread to the How-To section where it belongs.
Cheers :good:
Zer0C0oL said:
First off, before I get into it; nay sayers and trolls please keep the thread clear. Hopefully we can figure something and more minds together normally equal victory.
Last night an idea hit me, I use a hack with Windows that allows admin permissions and I don't have enough info about android apks to say that it wont work.
In Windows (yes I know they are way different) if you can figure a way to temp change one sys program to be command prompt, you can add users, change admin passwords, delete logs and the such. Basically you own the box at that point. Im not going to go into the details cause as far as I know M $ hasnt fixed it and I dont want them to.
So if we can find an apk with root writing permissions and can change it to be a term emulator we should be able to chmod root.
I have made some attempts, using the hidden menu apk. I figure it can change the prop file it should have root privileges; with no luck. Maybe I am not repackaging the apk correctly or something?
If someone that knows more about apks thinks it may be a possibility lets get to cooking!
Click to expand...
Click to collapse
I'm pretty sure it may be possible however impossible to avoid tripping knox.