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.
Related
How to Root the MyTouch Slide
v1.0 Brandt DeLorenzo 7/19/2010
(I tried to add links, but I couldn't because I was still a newbie on the forum...oh well)
Required Hardware
Windows, Linux, or Mac Computer
USB Cable
T-Mobile MyTouch Slide with SD card
Required Computer Software
ADB Drivers for your computer
The Android SDK
Command Line editor
Required Files
Root.zip
MyTouch Slide Rom(s)
Optional Apps
Rom Manager (by ClockWorkMod)
Any backup app from the market (like MyBackUp Pro)
Step 1: Install Required Software on the Computer
I. In order for your device to communicate with the computer, you will need the proper ADB drivers. ADB Drivers should install automatically when you attach your MyTouch Slide to your computer when using a PC. If you need to manually install the drivers for a PC, locate and install the HTC Sync Update program on your computer.
II. On the device, go to Settings > Application > Development and turn on USB Debugging.
III. Download the Android SDK and unzip the directory in your C: drive somewhere where you can easily find it. I’d also suggest renaming the SDK folder from android-sdk-windows to something shorter, like “asdk”. You do not need to install anything inside that SDK folder after you unzip it. Just move it to the C: directory and rename the folder to something short and easy to type, like “asdk”.
IV. You need to add the Android SDK Tool folder to your system path if you’re using a Windows PC. Go to Control Panel > System > Advanced > Environment Variables > In System Variables, highlight "Path" and click Edit. Add C:\asdk\tools to the end of the string. Be sure there is a semi-colon between the last entry and C:\androidsdk\tools. For example, it might look like this:
C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\asdk\tools
Then click OK on all of the windows and you're done with this step
V. Be sure that you have a working command line editor for your computer. For example, Windows users can go to Start > Run > (type CMD) > OK.
Step 2: Download and Move Some Files
I. Download the Root.zip file from Eugene's thread about rooting the Slide, unzip the contents (update.zip, ota.zip, and loop) and place them all in the C:/asdk/tools folder. This zip file contains all of the files that will unlock your MyTouch Slide and install the Recovery software to make everything easier in the future.
II. Find the MyTouch Slide Rom that you want to install. You may download as many as you want if you plan on switching between different versions of Android. You can find many of those Roms here or on AndroidSPIN. Download them to your computer and then move them to your SD card. They should be anywhere from 50MB to 150MB each.
Step 3: Preparing for Root
I. Before we begin the process, we need to test ADB to make sure your device can be seen by the computer. Connect your MyTouch Slide (it should be on right now) to your computer via the USB cable. Open up your command line editor and get to the Android SDK tools folder. If you named your SDK folder ‘asdk’, then you would type CD C:/asdk/tools and hit enter. You should see the prompt change from C:/ to C:/asdk/tools>. Type loop and hit enter.
II. If ADB is working, you will see a continuous loop of commands running up the screen. Hold down Ctrl+C to temporarily stop the loop and look for something that says:
List of Devices Attached
HT05RPS02484 Online
If you see something like this, type Y and hit enter. (Your device number may be different than display above)
If ADB is not working, go here to troubleshoot ADB and make sure that you can get the loop to detect your device before you go any further.
III. Perform a backup of any applications or data that you would like to restore. I’d suggest backing up applications, contacts, or any data that may not sync back to your device. You can find an application in the Android Market to complete these tasks. I prefer MyBackUp Pro.
*Mac and Linux users may need to put a ./ in front of anything that is typed in the command line. Like ./loop instead of loop.
Step 4: Beginning the Root Process
I. Power off your device. Hold the Volume Down Key and Press the Power button at the same time. Hold both buttons until the screen comes up in Bootloader mode.
II. In your command line editor, be sure that you are in the C:/asdk/tools> prompt. Type loop and then hit enter. You should see:
List of Devices Attached
HT05RPS02484 Offline
III. Select Recovery from the menu. Use the volume buttons to move up and down. Use the Power button to select the option. You should now see a dark screen with a black device and a red triangle with an exclamation point inside. Hold the Volume Up button and press the Power button. You should now see the Android system recovery (2e) screen.
If you kept the loop running, it should change to say:
List of Devices Attached
HT05RPS02484 Recovery
If it doesn’t change, unplug the USB cable from the device and plug it back in.
If your device number and “Recovery” appears, you can now stop the loop with Ctrl+C. If you do not see your device number and “Recovery”, you need to power off your device and try again. This may take a few tries.
IV. On the device, scroll down to Update.zip and select it using the Power button. It will display an error message that it failed. This should be expected and is part of the process.
V. In the command line editor, you should still be in the C:/asdk/tools> prompt. Type adb push ota.zip /sdcard/update.zip and hit enter.
VI. This is the most difficult part of the process. Type adb push update.zip /sdcard into the command line editor, but do not click enter yet.
VII. On the device, scroll down to Apply sdcard:update.zip and as soon as you select it with the Power button, click enter in the command line editor on your computer. The process should be all done within a second. If you did this properly, a new window in green text should appear with the title “Clockword Mod Recovery v2.5.0.1” or another version number.
VIII. Now you are in Clockwork Mod Recovery. First, scroll down to the partitions menu and make sure it does not say ‘mount system’. If it does say ‘mount system’, highlight it and hit the Power button to mount it.
IX. Scroll down to apply sdcard:update.zip and click the Power button to select it.
X. Power down the device. Follow the steps to get back into ClockWorkMod Recovery, but you won’t need to complete step VII. Simply select Apply sdcard:update.zip and hit the Power button to get back into ClockWorkMod Recovery in the future. (If a blank screen appears when you hit the Power button, press the Trackpad as the enter button.)
XI. On the computer, you should run the loop command to determine if the device is connected again. If it is, type adb install superuser.apk and hit enter. You have full root access.
Step 5: Installing a Rom
I. If you have already performed a backup of your files, you can now wipe the device from the ClockWorkMod screen. Scroll down to wipe data/factory reset and hit the Power button. You will be prompted with another screen with a Yes – delete all user data prompt. Select Yes – delete all user data and hit the Power button.
II. After the wipe has completed, scroll to install zip from sdcard and hit the Power button. Then scroll to choose zip from sdcard and hit the Power button. Now locate the Rom you want to install. Press the Power button to select the Rom and install it.
Managing your Roms
To make your life easy, download and install the Rom Manager application by ClockWorkMod. From this application, you can backup & restore your Roms, reboot into recovery with one click, partition your drives, and find new supported Roms for your device.
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
i agree, we've already got this pretty much in 2 different threads, in 2 different ways, one fully automated and the other manual. and i created a video and a tut that has more detail as far as how to install roms and such.. this is an unneccessary thread
Sorry man :/
where is my blow torch...prepare to flame
There is also ....
There is also a questionable step.
I cant get into Clockwork mod using the start update from the phone then push update.zip.
But if I adb push first, wait for the server to start, then updat from the power button on the phone, it works.
good luck.
nice guide! thanks
HighRidas said:
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
Click to expand...
Click to collapse
No offense, but I've tried many of the guides and they were difficult to follow when ADB was acting dumb on my laptop. The actual steps are easy, troubleshooting ADB on a Windows PC is a pain for most. Now that I have root and I'm using different roms, it's all easy and painless.
If there wasn't a no-linking rule on new user threads, it would have been much better...I agree.
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
tubaking182 said:
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
Click to expand...
Click to collapse
calm down bro !!! since i came to the slide side all i see is u going hard on people .. that ****'s not cool at all !!! it makes me wonder about u !!!
everybody got their pitch forks and torches out !!! just closed the thread that simple !!!!
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Well I thought this guide WAS Helpful to be honest! Not to mention lesstalk was just trying to help. Tubaking is always busting peoples chops everytime he says something it ends up being rude! If you dont have anything nice to say then go to a diff thread dude cause your sorry azz attitude just makes it so people dont want to post cause their scared of getting verbally bashed by folks like you! Being rude is NOT doing anyone any good and Im sure im not the only one who feels this way about you!
in my opinion they should be afraid to post, if they aren't then they make crap like this. i stated that he was trying to be helpful but without links this thread just takes up space and makes people ave to search harder to root thier phone. i am a nice person IRL, but i do not like wasted space. if someone has come up with a "easier" way to root then fine, but there is already a thread for preparing to root your slide, two threads on rooting your slide, and the slide rom bible which includes all of those threads, a stickie should be more than enough for most people and if not then they need to think before hitting that new thread button. there is no need for repetitive threads in the developement section. if there had been links in this thread(which i know he can't do as he is a new member) then it would have been fine and i would have shut up and left it alone, but right now there are two ways to root, one for computer people and one for script kiddies, either way if you can't get it to work with either method then you probably don't need root. if you can't read the simple walkthroughs then you don't need root, if you don't know what you are doing then you don't need root
EDIT: Here is the link to the thread that already covers all of this, and guess where i found it
http://forum.xda-developers.com/showthread.php?t=708522
I did find this thread helpful, especially since i'm new to android. I want to know what i'm doing and the only way i can learn what i'm doing is from reading many posts and lots of trial and error.
I have read both of the rooting guides from the rom bible, and there is still some stuff left out. I actually like this guide better than the others because there is more help in the whole ADB part of the root process.
Now, i know what i'm doing with computers, it still freaks me out how much i can do with computers. But in new areas where i want to learn, it helps to have more info than needed because people have different viewpoints on the same process.
@tubaking182 - for most of the threads you come in bashing in the dev section, i agree with you. But on this thread, i think you're way out of line. Yes there are 2 threads already and yes this thread needs links. But it's not a waste of space. I've lurked on xda since i bought and returned my HD2 (~late april). And when the slide was released, i headed to this subsection. And i've only seen it go down hill with more people posting threads that needn't be posted, but also with "wanna-be" mods flaming the person who didn't think and posted the needless thread.
But now that animosity has taken a turn for the worst and i only seen bashing in this section of the slide section of xda. And it's really making me want to leave xda.
The whole rooting process can be easy to learn if you've come from a previous android phone and have previously used ADB commands. But when you're really lost about even the whole linux folder structure (i'm not totally lost with this, but i'm more used to the desktop linux folder structure), then some of the guides out there to do certain tasks seem like another language.
3 guides for the rooting process can't hurt, especially when someone who doesn't know what's going on in the process wants to figure it out step by step and is too afraid of members like tubaking182 are always going on about searching for previous posts and flaming for simple questions (not that people shouldn't search for previous posts and threads).
EDIT: i do commend all the devs for their hard work making anything like rooting the phone remotely possible.
tething is, when you want to post an issue about something you saw in another thread, the issue should be posted there, it will be answered when people see it or when the OP has time to get on and answer. i am not trying to be a "wanna-be" MOD as i don't ned to be on XDA any more than i already am regulating posts and mergng threads when they should be merged, this thread holds ZERO new info and therefore should not be posted. if this member found a simple one-click root(which i hope to god never happens with this phone) and he wanted to tell us about it and tell us what he searched to find it and whatever else then great i ould not care, but some things do not need a new thread, if users all searched the Q&A section, the General section, and the Dev section BEFORE clicking the new thread link at the top then we would probably have half as many pages in the dev section, we have 8 pages now that i have gone through in the dev section and i have seen way too many repeat threads and questions. if you wanna see who i am take a look through my posts, i am a very helpful person when people want HELP, but when people want ANSWERS and they want stuff easier and they post in the wrong section then i get irritated and my messages are less helpful.
the number one reason n00bs post in here is because more people will see it, unfortunately this means the devs have to deal with the BS threads that push their stuff to page 3-4 and most people don't read past page two to look for a thread
yes, but you have to remember this is a very publicized and a public forum. In another forum i belong to, this happens all the time even though we have clearly marked stickies in every section.
I bet you most of the pointless threads have the OP posting only once and never even commenting on the posts made after they got the answer. That is what happens when you have a forum that's known for phone customization (or any public forum for that matter).
EDIT: and i'm not saying you're mean, i'm just saying it's going a little too far.
EDIT 2: if someone makes a thread only looking for answers that have been previously posted, just don't respond to it as that person won't ever be back. it's as simple as that.
@lesstalk - Thanks for the guide, outside of the lack of links(out of your control) this is a wonderful guide that I have started pointing new MTS users to.
@tubaking182 - Fact is, the guide on this actual covers steps that were skipped over in the other root guides because they were assumed to be common knowledge. Its that assumption which will kill future android users desire to learn about the device, especially when its accompanied by such a poor attitude from the "regulars" of the forum.
Outside of the links being missing due to being a new user account on the forum, the guide was more complete and comprehensive than any of the other guides so far. It managed to cover step(s) that are easily overlooked by someone who has rooted other android phones before, but CRITICAL to function and not mentioned in the other guides. I cant count the number of people I pointed to the pre-existing threads on rooting for MTS, who completely missed the superuser.apk setup because there were not any steps written for it.
A well educated userbase is a happy and quieter userbase, and while there are alot of useless threads in this section, this one actually served a purpose.
^^^
Here here!!
This is the first guide that has explained it all, and now I feel like I can do it too. I've done my g1, and tons of wm phones, but this one is completely different. All depends on your background.
You should be trying to expand and diversify the user base, not alienate it. or would you rather lock up the keys and argue with your self all day?
Sent from my T-Mobile myTouch 3G Slide using XDA App
I agree that this guide might Hold your Hand & even ( Might have missed steps ).
It's not my Job, nor any others person job to make sure you have your driver's setup & adb working correctly. There is plenty of other threads that already cover this, easy to find by using Google..
regardless, Thank you to the OP for try to help make things a bit clearer
~Eugene
tubaking182 said:
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Click to expand...
Click to collapse
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
dcowboys2184 said:
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
Click to expand...
Click to collapse
Ditto. This is a redundant and unnecessary post. There are more than four different guides and several other posts on preparation. Yes, they aren't written for a kindergartner, but rooting your phone isn't supposed to be easy. Do some research, read a post or several, and only post after your eyes start to bleed. Cluttering the forum makes it even harder for new members to the community.
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
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Benefits and change log:
Benefits:
Code:
You can now rerun the rooting script to apply whatever modifications you missed out on
You can now apply any mod using adb instead of file explorer
You can remount your system by just using "adb remount" instead of using a file explorer
Changelog:
Code:
2.0: Included needed files for extract / included busybox installer
1.0: Initial Release
Credits:
Code:
brianf21 for showing me how to extract files from an apk so now you can install directly from the app and nothing else is needed except root.
Nemith for the adb daemon
Myself for the app, hijack method, and testing
puellanivis from IRC for being terrible at communication and also help with a few of the commands
This one is mine as well.
damn you, I am taking this one for video! click comment for video
Firstly,
Thanks Indirect, you make my Nook a joy to use. Many thanks also to Albertwertz - your Youtube videos are helping a noob like me get up to speed with this Android experience.
Can't post this in the Developer thread (still under 10 posts) but there seems to be a problem running the nookandzergy.bat file whilst running the ADB Hijacker. I'm getting a dos error:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
Having a quick look at the bat file I can't see where %adbr% is being set to "yes".
Update: After making sure adb hijack was running, I tweaked the batch file, forcing adbr=yes. The script then worked and allowed me to replace the SystemUI.apk to remove the B&N Home button. Not sure how Indirect intends to set the variable properly, but by adding:
set adbr=yes
above the line:
if %adbr%==yes goto N1
Allowed by to re-run the rest of the root process
Another thing I did notice when testing the script was that by selecting "N" to the "Do you want to replace the systemUI to have a perm back / menu button on status bar and have the N button goto home on first click?" question the script errors with a -N7 not found.
I am having the same problem. I followed the video that albert posted and even opened up the cmd line to double check my adb remout. Everything worked fine till i get:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
I don't know if Nook&Zergy is setup to support the adbd hijack yet. But that is the most likely answer. Or in particular, you might not have the newest N&Z as well.
I also wanted to momentarily divert the thread, and mention that snowball-mod already includes this adb-hijack, so it is unnecessary to run it on snowball-mod. (However, Indirect worked with me to ensure that it wouldn't hose anything if you did.)
Before I ran nz, i downloaded the latest from Indirect's original root thread. If the updated one isn't using that link, then where do I find it?
Indirect and I were up kinda late last night working on this and he made several modification on my nook zergy extraction that he may have forgotten to make when he remade his and uploaded it for everyone. Here is a link to the mod he made of the latest nook zerg on my pc. This may have something that the new one doesnt that he forgot to do. I am sure he will fix the code soon, but until then, download and try this: http://dl.dropbox.com/u/24100179/Nookie/NookandZergy.bat
this is the nook zergy bat file he modified. copy it and replace the bat file in your new nook zergy extraction and see if it runs right with this app
This is only temporary, dont use this after he fixes it
That did the trick! Thanks Albert!
I just got my nook & I don't understand the programming that you are talking about. But if you both were up late working on the root script (assuming). Just an FYI once I finished w/ the driver loads & started loading the root script, my device wouldn't show up, did a factory reset 3 times, as well as removing any usb traces etc... finally got it to take & all the red stopped & never loaded in the gapps, launchers etc... I reloaded it again & it says that I am rooted, but having a heck of a time w/ Titanium doesn't want to accept any of the
devicemanager .apk stuff. Sorry for no tech terms, Indirect & Albert Thank you so much for making this easy. Loved the video, really helped a ton. Just wanted to say thanks & let you know of the glitch.
I got it loaded now it is not recognizing the sd card 4 Titanium. I have done several of your factory reset, as well as the b&n reset still nada even put in 4 different cards. Happy New Year & Thanks for any help
TRI
did this today, easy, took 5 minutes. Grateful for all this
I'm a little bit confused, my nook updated to 1.41, i've tried downloading adb hijacker to my nook, but it won't open, what am I doing wrong?
Edit: What exactly do I need to do to block the updates and allow my nook to use the android market again?
I'm a pathetic no0b, and I tried downloading the ADB hijacker to my nook, but it won't open. What do I need to do to fix this?
Thank you.
ETA the Nook updated the other day.
Indirect said:
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Click to expand...
Click to collapse
absolutely awesome!
Guys, this doesn't stop updates or is usable on the 1.4.1 update..it's a 1.4.0 modification that hijacks the adb daemon on the device.
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
nearlyno0b said:
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
Click to expand...
Click to collapse
^^^^^ Quoted for the sake of others ^^^^^
arkraven000 said:
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
Click to expand...
Click to collapse
Below is a link to the information as to how to remove B&N 1.4.1 update and restore 1.4.0:
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard
ENJOY!
Note: more content is coming regularly, so check back regularly! Also, post your input so this thread does not become buried.
As an initiative to kickstart development for the Galaxy Player 4.0, I have decided to put up this guide to try and attract more users to rom development. This, although, does not mean you can willy-nilly post up a rom including one mod, or a quick tweak. Making a rom involves a lot more than that.
The Developer's Code:
1. Your rom MUST be unique from the other roms.
This means you have to have a careful, well thought out rom. It must have several things differing it from other roms, something that makes it stand out. The last thing we need are 200 "me too" roms cluttering up development. Takes Klin's rom and mine, for example. We both have ICS themes, we both have tweaked our roms for performance, but they are both completely unique. Why? Because we didn't copy one another. We saw what the other had, and left it alone. I have an ICS theme, he has an ICS theme, but they are based on completely different themes. The biggest boo-boo in rom devving is copying someone else's rom/features/work. You will get kicked out unbelievably fast if you DO NOT follow this rule. To reiterate, the last thing we need is 200 identical roms. Make sure yours is unique from the others, and has a defining feature.
2. You must be willing to provide regular, consistent updates.
Maintaining a rom can be a full time job. You have bugs to deal with, features to add, and hours of work in which you only accomplish a small amount of work, due to some catastrophic failure. Last night it took me over 3 hours to fix a battery icon issue. Why? because I had almost space left in which to apply my fix, and if I did even one step wrong I had to reflash to correct the issue.
You should NOT release your rom once, and never look at it again. You should be willing to update it at least twice a month, if not sooner. I update mine several times a week, but that's because I have a lot of free time. Your mileage may vary, but try to hit for that mark. Too long wihtout an update and users will get bored/tired of your rom without anything new to spice things up.
3. You must be willing to provide helpful, friendly support.
At times, monitoring your thread can be frustrating. you may have someone complaining about an issue that was fixed several releases back, or someone who wants a new feature and keeps bugging you about it. It can be frustrating at times, but make sure you calmly answer everyone's questions in a fair manner. It can be extremely frustrating for a rom user to post up a question, and have it answered days later because the dev was "too busy" to monitor their thread. This, if anything, is almost more important than rom updates. Users love devs who actually converse and answer them, so be friendly, and keep your thread going!
4. ALWAYS ALWAYS ALWAYS give someone the apppropriate credit for their work.
It is the bane of the dev's existence: spending days/weeks/months of xyz feature/theme/rom, and have someone come along and snatch their work from them without as much as a "thank you". First of all, it will get you banned faster than any other offense out there. Secondly, it is one of the largest insults you can give someone. Our community is one that is supposed to share work, and most people do that freely, but you MUST give credit where credit is due. It is best if you ask someone's permission before you use their work, especially if it is something major (a huge theme for example). But even if you don't (and you should), at the very least list their username and what they did in your rom SOMEWHERE in your description.
5.You do not know everything.
After creating a rom, many people feel that they know much more then the "average" community, and that they are always right when it pertains the their rom. This could not be more wrong. The best way to improve your rom, is to listen to xyz person who knows more about a certain area than you do, and attempt to learn from that person. Everyone is skilled in a different area, so if you listen to your community, and assume they know best, you can learn and accomplish a lot evry quickly.
6. Google is your friend.
Do not assume that dev's know everything, and that they pull these features out of their heads. When in doubt, go to google. Always. There is normally a guide, or someone with your issue to help you out. As usual, make sure you give that person credit if you use their work.
So, to sum it up, Make your rom unique, be dedicated to your work, be ready to handle unexpected situations, ALWAYS give someone appropriate credit, listen to your community, and google a lot!
Not intimidated yet? ready to bring your amazing idea to the limelight? head on down to the section below to get started!
The Easy Way to Dev: Odin flashable packages.
Most people don't want to edit their rom on their computer. As a matter of fact, you can create a killer rom without even touching a computer to mod it. Up until I started theming, I working on my rom 100% on my device. This is the most tried-and-true method out there, and the one most likely to create the least drama. All you have to do is Pull the /system partition from your Player, and create a tarfile out of ti.
Prerequisites:
Samsung Device (system partition location may change with device type. This should be the same for US/INTL players)
PC running Ubuntu/form of linux (ubuntu is recommended for beginners)
ADB installed (actually not needed, but speeds up the process) (look below in resources for a guide)
appx. 300mb free on /sdcard
about 1 GB free on the Linux box
1. Apply whatever mods you want too
2. Open up a terminal emulator
3. type this in: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
4. wait for it to complete (may take up to 10 minutes)
5. You now have a file called factoryfs.rfs on your internal sdcard
6. Hook it up to a computer and activate usb storage
7. copy factoryfs.rfs to whatever directory you want (home is recommended for simplicity)
8. Open up a terminal
9. cd to the directory of your file (if you placed it in home skip this step)
10. Type in "tar -H ustar -c factoryfs.rfs >packagename.tar"
11. Now you have a odin-flashable rom!
ADB users, simply run adb shell and type in the first command, then adb pull the file to the computer.
If you want to save space for a file sharing website (eg. mediafire, which has an upload cap of 200mb), simply Zip the file using 7-zip (set on ultra). You may have to do this on a windows machine.
Now this is even easier! simply flash the stock image in the link below with all the essentials included, and you can apply all the mods you want without having to ever go through dsidxa kitchen! Klin even fixed busybox for you! this way you can easily start from stock and work your way up to more advanced hacks.
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
The Advanced Users Guide: CWM packages.
Maybe you want more flexibility. Maybe you need to deodex your rom to mod some stock files, or zipalign to speed things up. This guide is for you people who need the more advanced options. It is harder, and you have a greater chance of messing things up, but you get to completely control your rom, even easily edit it on the computer! This guide is for advanced users only, or someone who is willing to spend a lot of time on trial and error.
Prerequisites:
ADB installed (Extremely helpful, and may to required)
Samsung device
Ubuntu/linux box
A bit of caution
Patience
1. Install Dsidxa Kitchen
2. Put your factoryfs.rfs in the necessary folder
3. cd to the directory you installed the kitchen
4. Type "sudo su"
5. enter your password
6. Type "chmod +x menu"
7. run "./menu"
8. you are now in the main menu of the kitchen.
9. There are many options, choode the one that you need!
Note: stay away from installing busybox using the kitchen. It installs a bad version of busybox which can make rom development a big headache for you!
10. There is a working folder in the kithcne directory, in there mod all the files you need.
11. When you are done, head into option 99 (create rom)
12. Run the interactive option
13.When you get to the update-script type, type "y" to install the newer type, which is required to flash a cwm zip in the Galaxy Player.
14. If you want to flash your rom using stock recovery, sign it. Else, leave it alone.
15. You can keep the normal name, or change it to what you want. If you are going to be flashing using stock recovery, make sure it is named "update.zip"
That is it! If you want to create a odin package out of it, simply flash the cwm zip, then follow the instructions above!
I will be adding on to this guide as time goes on, so make sure you ask pertinent questions below!
Resources/Additional Guides:
Install ADB:
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Install dsidxa kitchen:
http://forum.xda-developers.com/showthread.php?t=1303311
4.0 base (essentials installed, just apply your hacks and you are good to go! thanks klin):
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
Easy theming guide:
http://androidforums.com/optimus-m-...guide-theme-guide-noobs-adding-lots-more.html
APK multi-tool (needed to theme):
http://apkmultitool.com/?q=node/5
Recommended hosting sites:
www.mediafire.com
Good Rom practices:
1. If you retheme, include screenshots! people love screenshots.
2. Make a logo if you can, it makes it easy for people to support your rom by adding it into their signature.
3. If you mod, make sure you can easily explain it to someone if need be. Messy hacks are not good in the long run!
4. Focus evenly on all parts of your rom. Some people love speed, others love features. You can focus on one or the other but try and keep it balanced.
5. If you create a custom script/init,d script/documentable file make sure you include comments in your mod so people can try and fix it if need be!
6. Make sure all the bugs are ironed out before release. People love fast releases, but if it is really buggy they may switch to another rom.
7. if you have exhausted all other methods of fixing an issue, or cannot work on it a lot in the opcoming days/weeks, release a beta version stating the bugs clearly. That way while you are gone, more experienced people can help you iron out the bugs.
8.Make sure it is easy for the person to obtain your rom. If they have to download another utlity or click through 30 ads, they may just want to use another rom than go through the hassle. Worse, they may mess it up, forcing you to help them troubleshoot.
9. Make sure you update utilities on your rom as soon as an update becomes availible. That way you get the fewest bugs, and as I said before, users love updates!
10. Even if someone's issue seems isolated, at least spend some time with them figuring out what happened so they can fix it. You never know, it may be the harbinger of a HUGE outbreak of issues.
11. Base your rom on an intl version. There is a fortunate "bug" that klin discovered that allows US users to use any intl rom without their home button breaking. Of course, that has a lot of asterisks, but if you will look below, I have developed a fix for that issue, which allows anyone with a "broken" home button to use it with the problematic rom!
12. Practice good rom devving. If there is a major issue that could be a pain, don't take the easy way/fix out. That always comes back to bite you later, as I have figured out. I once had a corrupt journal on my system partition, and did not want to go through the hassle of recreating my rom on a clean partition. So, I simply added a flag to have /system mount as rw if there are any issues. Sure enough, about 3 days later, I started having some filesystem issues, and had to completely rebase, because I did not have any backups.
13. ALWAYS keep backups. Just do it. Not just one, either. Keep at least three days worth of backups, just in case there is an issue in backup 1 and two, but it not in no. 3. This would have been hugely helpful to me in many cases, but I didn't want to "waste" the space. Guess what I did a few days later: spent a nice evening with linux fully recreating my rom from scratch. Just do it.
Fix home button issues. (useful if you use a rom seperate than a flasher's region) (developed by me)
I have finally, after a bit of luck and some know-how, determined a fix for the home button issue! This will work on ALL roms, not just this one, and will probably work for the 5.0 as well. This also means you can fully wipe data if you want, and simply apply my fix.
1. Navigate to /dbdata/databases/com.android.providers.settings
2.Optionally copy to a computer (easier that way)
3.Open it up in a sqlite editor (if you are doing this on the device, copy it to /sdcard and and then copy it back
4.Navigate to the locale/first section (there should only be one string in there
5.It should look like en_US if you have a US player, or en_GB if you have a UK/intl player
6.Change the string to the language/locale you use (if you are INTL you can merely change it to xx_GB, where xx is your language. If you are US, just perform the same steps, but change the last part to US)
7. commit/save the file and copy it over the old one
8. Reboot, and your home button *should* be fixed!
NOTE: I have not personally tested this. It has a 99% change of working, but I have yet to completely verify it.
NOTE: after you replace the file, android may go a little haywire (wifi disconnects, forgets password, advanced reboot option unavailable, etc.). THIS IS OKAY. Simply reboot, and it will all be back. Do not change any settings after copying until it reboots, as it may possibly break the fix
NOTE: I cannot provide a downloadable file, as that file contains all of your system settings, and if you use mine, my settings will be applied, which could be pretty bad in some cases.
NOTE: this has no chance of bootlooping or bricking your device. At absolute worst, you have to set up a few settings/restore from a /dbdata backup. There is almost no risk involved.
Potential fixes for potential issues:
1.Bluetooth breaks. The main cause of this is if you install supercharger and nullify. Simply unullify and verify it is remove from build.prop, and you are good to go!
2. Home button breaks. (see above )
3. Root/busybox breaks. It's kinda messy, but if you absolutely HAVE to, simply reroot. That should fix it in a pinch. This is a classic case of keeping good backups. I have had to spend an entire afternoon redoing my entire rom because of my lack of recent backups. If you have the space, keep them. I have more than once managed to create a stopgap solution in my rom just to have some weird issue pop up again, and again. Just do it.
I LOVE you, man.!!
Hanthesolo,
Very good achievement, we all have to learn from your good sharing.
Congratulations man
rgds
I am really happy you guys like this! I will continue to add to it as time goes on, so expect even more content!
Sent from my EtherealPlayer.
New content up! also notice the link to the stock rom klin made so that you never need to go through a kitchen to get your rom started!
Has anyone used this yet? successes/failures? make sure you give me feedback so I can make this better!
Yet mre content up! Could this be possibly stickied? I know it's a little rough right now, but noone replies to this thread as there really is nothing to reply TO. I have worked hard on this and would hate to see this information go the way of the dead threads.
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
iAMsalm said:
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
Click to expand...
Click to collapse
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
hanthesolo said:
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
Click to expand...
Click to collapse
I know it definitely feels like that from time to time, but that's a byproduct of the nature of our devices. There's ridiculous money in selling someone a shiny new crippled phone with a horrific contract that will never get updated. You won't see a jawdropping ad on TV featuring a Galaxy Player because there's just no money in it. I'd love to have the T-Mobile girl holding my phone while wearing a pink leather riding suit(her, not me). That ain't happening.
I'm pleased and more than a little shocked that some new roms have come out in the past month thanks to this guide. I wanted a Android powered phone without the contract. I wanted an iPod Touch without all the bull**** that comes from being tied to Apple. Thanks to XDA my device fast, sexy as Hell, and does everything I want.
The only thing that makes me sad is that a year from now I probably won't be able to buy a Galaxy Player 4.0 v2 because there's just too much money to be made from contract only devices.
Thanks for this guide. It help me for begin android development.
GalaxySWifi4 said:
Thanks for this guide. It help me for begin android development.
Click to expand...
Click to collapse
I hope you have fun beginning development! It really is a lot of fun once you et past the basics.
Gswifi, I never replied to you, but your speech was so awesome, that I want to put it in the OP .
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
@hanthesolo
do you have some knowledge about kernel compiling, so you could hel me?
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
please do
I understand early nothing about this advanced stuff of making ROMs, even more about make Kernels XD. But I want to experiment some little things to learn by myself step at step. But... I cannot start... I'm in CM10.1 with Koala's Kernel and I can't make the factoryfs.rfs file doing this: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 in Terminal Emulator because /dev/block/stl9 doesn't exists. With ADB I have the same error.
Is this due to this ROM is not stock or something like this? Or only I have to create this folder or change it by other...
---------- Post added at 02:55 AM ---------- Previous post was at 02:37 AM ----------
I'm trying to do this but without if=/dev/block/stl9. I don't know if I'm doing well...
How about some info on modifying or tweaking already compiled roms?
Say you want to remove some of the apps included with CoolDevXYZ's rom or modify some of the settings pre-install (e.g. build.prop tweaks, etc.). How do you tell the kernel these changes are intentional, not the result file corruption, infection or something?
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.