Related
I wonder if other people are having these issues, story follows.
I was trying to install the updated ADW.launcher via the adb install command and was getting errors such as "/sbin/sh pm not found". This led to an investigation and it turns out that all the standard applications used to install stuff under android are in /system/bin BUT... The path in the CM6 rom does not have /system/bin in the PATH variable. The only path element as far as I can tell is /sbin. So the solution I came up with was to copy over all the tools from /system/bin to /sbin and this worked.
So here is the real question. How do I change the path on the android device? I have already tried export PATH=$PATH:/system/bin but this does not stick after I close the adb shell.
Update: oh great when you reboot the phone all the copied tools disappear and you have to do it all over again to install another file. Did not expect that one. This makes my need to change the path even more urgent.
Update2: I found it easier to just push the new file over top of the old one in /system/app. This will work for system apps and if I need to install other apps I can just load them from the sdcard.
Is there a reason you are not installing it from market? ADW is the default launcher in CM6, so the one from market is not the same, but they can coexist.
so the one from market is not the same, but they can coexist.
Click to expand...
Click to collapse
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
anika200 said:
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
Click to expand...
Click to collapse
It is in the path.
# echo $PATH
/sbin:/system/sbin:/system/bin:/system/xbin
#
Can you help me to change the path? Mine is only /sbin for some reason.
Normal export command did not work for me. Thanks
Maybe its baked into the boot.img? What about the init scripts? Any clues where to start? Maybe I will just flash on a new nightly, would that over write the existing path info?
Ok, I found some clues. A document on the android init scripts describes the path settings. I will poke around in there and see what I can muck up. http://www.netmite.com/android/mydroid/1.6/system/core/init/readme.txt
Sent from my Liberty using XDA App
Answered my own post.
To change the path you need to edit init.rc and add the correct path.
For some reason the nightly I was using had the wrong path in there and would not let me use adb install correctly. I would get an error back "/sbin pm not found". The adb installer was looking for a tiny program (a shell script really) named "pm" but it could not find it because pm is located in /system/bin which was not in the search path. Probably would have caused other problems too.
On a side note, why could I not get an answer to this simple question on a developement thread. Seems like rom creators/moders would know this second hand. Not complaining just makes me wonder.
Sounds a lot like a complaint to me.
I've been busy working on issues that are not isolated to a bad nightly, such as why we can't read telnos and contacts from the sim card.
/system/bin/sysinit gets pulled in from the cm6 repository, so things on nightlies are very fluid - I never know what to expect. Looking at my build, there is no way I could answer your question in any definitive way that would explain the discrepancy. Since I could not verify the problem, I deemed it a non-issue and moved on.
That did sound like a complaint, sorry. It was not really directed at you as I assume there is more than one developer on this site. I got it solved no problems. Maybe this will help someone else down the road. I have seen a few of these posts around and never saw a concrete answer.
I am surprised the phone ran so well with the path mangled so bad. I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
anika200 said:
I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
Click to expand...
Click to collapse
I was a little surprised as well.
Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems
This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851
Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?
Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).
Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory
Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.
I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App
Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.
I see so many having problems trying to get S-off on the 1.55 HBoot. Some have had none but I've posted this response so many times I thought I'd make my own post and hopefully people's searches will direct them here and it helps them.
I am no developer or coder or anything but a techno junkie. I have no linux experience except what I've taught myself so be sure if this 47 year old, self taught mother can do this then anyone can.
Just take your time, pay attention to what you're doing, and read everything before you hit go.
I had no luck with rumrunner on Windows 7 or Windows 8/8.1. Drivers were never right. Couldn't get rid of HTC one sync. So I finally got myself
(1) a copy of 32bit Ubuntu. NOT 64!! http://www.ubuntu.com/download/desktop
(2) no need to install-boot into it as if trying it (IMAGE 3)
(3) grab rumrunner for Ubuntu (linux) http://rumrunner.us/
(4) drivers NOT needed
(5) turn off fastboot (IMAGE 2) You should also turn off any lockscreen security....
(6) turn on USB debugging in development settings (IMAGE 1) You should also turn off any lockscreen securtiy
(7) run rumrunner (instructions are on the rumrunner site) paying attention in case extra permissions are required by superuser http://rumrunner.us/instructions/ (See Ubuntu section below)
(8) sat back and watched the magic. Worked the first time.
I know others have had zero issues but some of us have had nothing but nightmares. This is who I'm sharing this for.
I hope it helps... Even just one!
Have fun all!
IF BY CHANCE YOU ARE HAVING ISSUES WITH ADB OR FASTBOOT IN UBUNTU SEEING YOUR DEVICE, TYPE sudo BEFORE YOUR COMMANDS. IT WANTS PERMISSION TO ACCEPT YOUR COMMANDS. WHEN YOU TYPE sudo THEN YOUR PASSWORD YOU ARE GRANTING THOSE PERMISSIONS. SOMETIMES THE ISSUE WON'T APPEAR TIL YOU GET INTO FASTBOOT. SO CHECK FIRST BY TYPING IN adb devices WHEN YOU FIRST OPEN THE TERMINAL. IF YOU GET A SERIAL NUMBER YOU SHOULD BE FINE. AFTER YOU GET INTO BOOTLOADER, TYPE fastboot devices IF YOU GET A "no permission" ERROR THEN YOU NEED TO TYPE sudo BEFORE all INSTRUCTIONS. SOME VERSIONS OF LINUX HAVE AN SU TERMINAL. THAT WOULD BE THE BEST TO USE AS IT REQUIRES ROOT/PERMISSION TO EVEN START AND WILL MAINTAIN THOSE PERMISSIONS THROUGHOUT.
UBUNTU STEPS.....
Image 3- Boot into Ubuntu
Image 4- Download Linux version of rumrunner
Image 5- Extract Rumrunner (Right click on the zip and select extract here...I left it in the Downloads folder)
Image 6- Inside the extracted Rumrunner file
Image 7- Open Terminal in Ubuntu (Top left gear like symbol, click it and a search bar will appear, start typing terminal, it will appear below the bar, just select it)
Image 8- You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Image 9-12 Shows how the terminal should look as it finds, downloads and install the appropriate files.
Image 13- After the downloads are finish you can check to make sure things were installed correctly. Type “adb” and your screen should look like this
Image 14- Type “fastboot” and this is the information that should appear.
Image 15- To make sure your device is seen type “adb devices” and it should show devices with a serial number.
Image 16- Now make your way in the terminal to your downloads folder and into the rumrunner folder by typing the following BOLDED commands in the terminal
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ cd rumrunner_HTC_0.5.0
[email protected]:~/Downloads/rumrunner_HTC_0.5.0$
(This line simply indicates you are in the rumrunner folder)
Image 17- Now you need to run the command to get the party started...it is in bold
[email protected]:~/Downloads/rumrunner_HTC_0.5.0$ sudo ./soju
Image 18- Confirm you understand what it is you're doing or at the very least you are willing and accept the risks by typing “Yes”. It must be “Yes”. It will not accept yes, y, ok or anything else. The Y must be a captial.
Image 19- After you type Yes the second time things get under way. Be patient. It may take a bit of time. Just pay attention in case you are asked for extra permissions.
Image 20- S-Off verification
After the second Yes rumrunner does it's stuff...it can take a while. Be patient. Pay attention in case you need to give permission. DO NOT DISCONNECT YOUR PHONE until you either get the ok or are told it failed.
This is as clear as I can be and I hope it makes it even easier....
Suggested by @chp , you may need to go into software centre (selected by opening the search bar again and typing software centre), edit tab, software resources and making sure that "Community-maintained free and open-source software (universe)" is selected.
ALSO, PLEASE GIVE CREDIT IF YOU USE THIS. FEEL FREE TO SHARE IT, JUST LET PEOPLE KNOW WHO ACTUALLY TOOK THE TIME TO CREATE IT. UNLIKE THIS PERSON... http://www.usofttech.com/t152630.html , WHO HAS EVEN TURNED OFF REGISTRATION SO I CAN'T EVEN MAKE IT KNOWN THERE.
THANK YOU!!
tobesedated said:
I see so many having problems trying to get S-off on the 1.55 HBoot.
Some have had none but I've posted this response so many times I thought I'd make my own post and hopefully people's searches will direct them here and it helps them.
I had no luck with rumrunner on Windows 7 or Windows 8/8.1. Drivers were never right. Couldn't get rid of HTC one sync. So I finally got myself
(1) a copy of 32bit Ubuntu. NOT 64!!
Click to expand...
Click to collapse
I like what your doing here
the instructions on the rumrunner site are very vague and it took me quit sometime just to figure those things out when you know very little about linux.
original post updated with more concise instructions and pictures.....the easiest way to show the steps i took
Removed an extra picture that may have caused confusion
tobesedated said:
Removed an extra picture that may have caused confusion
Click to expand...
Click to collapse
nice work :good:
just a question, you didnt even need to install adb & fastboot?
nkk71 said:
nice work :good:
just a question, you didnt even need to install adb & fastboot?
Click to expand...
Click to collapse
OMG!! Yes I did...and now I shall update for that as well...Thank you so much for ponting that out
tobesedated said:
OMG!! Yes I did...and now I shall update for that as well...Thank you so much for ponting that out
Click to expand...
Click to collapse
Keep up the good work , and thanks for helping!!!
in case this helps save you some time:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
nkk71 said:
Keep up the good work , and thanks for helping!!!
in case this helps save you some time:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Awesome thanks and I just went through a partial run of rumrunner's so I could get the screenshots lol
And it's my pleasure
Op updated!!
Original post has been updated. Added instructions to download and install adb and fastboot in Ubuntu. More pics too LOL YAY!!
Good luck everyone...feel free to hit thanks if you get anything out of this
[email protected]:~/Downloads/rumrunner_HTC_0.5.0$ sudo ./sujo
Click to expand...
Click to collapse
you have mistyped command, the right is: sudo ./soju
janda said:
you have mistyped command, the right is: sudo ./soju
Click to expand...
Click to collapse
Thank you for pointing that out... Correcting it now
Sent from my LG-D803 using xda app-developers app
Nice work on this guide and thanks for taking the time to write it up
By the way, I've moved this into General as it's more suited there and won't get buried within the forum quite as quickly
Regards,
- KidCarter93
Forum Moderator
KidCarter93 said:
Nice work on this guide and thanks for taking the time to write it up
By the way, I've moved this into General as it's more suited there and won't get buried within the forum quite as quickly
Regards,
- KidCarter93
Forum Moderator
Click to expand...
Click to collapse
Thank you... I wondered where it went lol
Sent from my LG-D803 using xda app-developers app
Fixed the incorrect soju command
Sent from my LG-D803 using xda app-developers app
how is this working on 64b ubuntu as im all ready rocking 13.10 on my laptop and dont want to reinstall just for this
skedone said:
how is this working on 64b ubuntu as im all ready rocking 13.10 on my laptop and dont want to reinstall just for this
Click to expand...
Click to collapse
You don't have to install... You select try from a disc. You can try on 64 but according to rumrunner site it isn't supported. Doesn't mean it won't work just that if it doesn't they can't help you
Sent from my LG-D803 using xda app-developers app
I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.
chp said:
I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.
Click to expand...
Click to collapse
Thanks for that in case anyone needs to do this... I didn't. I followed exactly as in my OP but this is a good to know in case someone runs into issues.
Sent from my LG-D803 using xda app-developers app
Original Post updated to include a suggestion by @chp ...thank you. And a little rant by me lol
Have a good one all!!
chp said:
I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.
Click to expand...
Click to collapse
tobesedated said:
Original Post updated to include a suggestion by @chp ...thank you. And a little rant by me lol
Have a good one all!!
Click to expand...
Click to collapse
I think that's needed for 13.10 right? on 12.04 LTS, the other repository should work fine. (at least it does for me)
cheers
I have a Nook Simple Touch, BNRV300, and I have successfully modified uRamdisk to gain root shell access with ADB over USB (Thanks Renate!). I am currently on firmware version 1.2.1.
I know this may seem like heresy to some here, but I really do not want or need to root my NST and add a number of apps I won't use anyway. I have a fully rooted Nexus 7 for that sort of thing.
All I would like to be able to do is turn off the need to swipe to unlock when returning from sleep, and modify the text on the screensaver overlay.
I have discovered, by the way, that sqlite3 does not seem to be available on this NST, as when trying to use it via ADB shell, it says "sqlite3: not found".
SO, there we are... I would greatly appreciate any assistance offered.
MildBill
P.S. I have tried Nook Manager, and while it did what I wanted, there were many things added that I just have no need for. And, battery drain seemed to double.So, it had to go.
Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://forum.xda-developers.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.
Renate NST said:
Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://forum.xda-developers.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.
Click to expand...
Click to collapse
Ahh, once again, thank you Renate. Now if I can get some idea on my main questions...
There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.
I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).
Code:
C:\>adb pull /system/framework/android.policy.jar
C:\>apktool d android.policy.jar \AP
C:\>mergesmali /v C:\AP\smali C:\Nook121Patch\KeyguardViewMediator.smali
C:\>apktool b C:\AP android.policy.jar
C:\>adb shell stop
C:\>adb mount -o rw,remount /dev/block/mmcblk0p5 /system
C:\>adb push android.policy.jar /system/framework/
C:\>adb shell chmod 644 /system/framework/android.policy.jar
C:\>adb shell reboot
Renate NST said:
There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.
I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).
Click to expand...
Click to collapse
Well Renate, I hate to complicate your answer any more than necessary, but...
On the Temblast page that clicking on your signature takes me to, I do see mergesmali, one of the two tools I will need based on the instructions you gave. I do not see nook121patch.zip, nor apktool, however. Where can I find these?
Also, can you tell me something about what this will do for me?
I hate to be such a noob, I have just enough knowledge to be dangerous. Thanks again for all your help, sorry I have to keep asking for more.
MildBill
Well, I wasn't that clear.
mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://forum.xda-developers.com/wiki/Apktool
There are many patches in the nook121patch.zip
You can apply them selectively.
.jar is easy, they don't need signing.
.apk is trickier they must be signed.
System .apk is even trickier, they must be signed with the system signature.
The KeyguardViewMediator.smali will make that your Nook just opens with a push of the power button and no swipe.
Renate NST said:
Well, I wasn't that clear.
mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://forum.xda-developers.com/wiki/Apktool
Click to expand...
Click to collapse
Ahh! Well, my bad, I should have tried harder. And, yet again, thanks. Nook users owe you much, Renate!
MildBill
Renate NST said:
Code:
C:\>adb pull /system/framework/android.policy.jar
Click to expand...
Click to collapse
OK so far, and (I think) I have apktool properly installed, then realized I also needed to install the Java Development Kit as well to use it, which I managed to do. But, when I try to do
Code:
C:\>apktool d android.policy.jar \AP
I get
Code:
Input file (\AP) was not found or was not readable.
as a response.
So, I guess I need to return to the magic well of your knowledge for further assistance and/or instruction.
To which I can only add...
HELP!
EDIT: By the way, I am using an adb.exe implementation from another root kit I have installed, not the standard installation from the SDK. Is this perhaps part of my problem?
Well, something goofy is going on there.
Type just apktool and get the usage and version.
\AP in this case is the destination directory.
It should not already exist or else you get a warning.
Maybe the input file (the jar) can't be found, but the error message is wrong?
Code:
C:\>apktool
Apktool v1.5.2 - a tool for reengineering Android apk files
Copyright 2010 Ryszard Wi?niewski <[email protected]>
with smali v1.4.1, and baksmali v1.4.1
Code:
C:\>apktool d C:\nook121\system\framework\android.policy.jar \AP
I: Baksmaling...
I: Copying assets and libs...
Code:
C:\>apktool d C:\boguspath \BogusDir
Input file (C:\boguspath) was not found or was not readable.
Renate NST said:
Well, something goofy is going on there.
Type just apktool and get the usage and version.
Click to expand...
Click to collapse
Well, there ya go... I got apktool v2.0.0b9.
I can get 1.5.2, but will it work with Java 7? Oh well, live and learn I guess...
MildBill
Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.
To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.
Renate NST said:
Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.
To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.
Click to expand...
Click to collapse
Well then, since it appears from the changes that 2.0 requires the Java 7 SDK, I guess I'll uninstall it all and get 1.5.2 and Java 6.
I'm running desktop applications:
Code:
C:\>java.exe -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing)
I'm compiling Android applications with:
Code:
C:\>javac.exe -version
javac 1.6.0_38-ea
apktool runs under the JRE, version 1.7 is fine.
OK, finally got around to completing the instructions as posted, and except for having to add the command 'shell' to the mount statement, everything worked fine. And, it accomplishes exactly what I was after.
Next I may look into trying your library and reader apps.
Thanks again!
MildBill
P.S. You might consider rewriting the readme file included in nook121patch.zip to better describe what each patch does.
The readme is admittedly very old.
That's because I forgot that it's even there!
Each of the individual smali files has comments at the head saying what it does.
I'll make something to compile the individual comments into a single readme.
I can also report, at this point, that unlike an other method I have tried to accomplish this simple task, this one does NOT run thru battery life like it was going out of style.
The next most popular option, NookManager, which uses the NookModManager to do this fix, uses an average of 10% battery life every day, even when in in sleep mode the whole time. Turning the option off (I.E. reinstating the swipe to unlock) again reduces battery drain to a more normal point.
But, the fix by Renate seems to use nomorebattery than the stock reader, whether reading, sleeping, with WiFi on or off. I like it!
Once again, Renate, thank you very much for this, and for all you have done for the Nook community.
MildBill
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Not a newbie tutorial at all. You might want to appropriately title this or add instructions to make it newbie friendly.
cangcan said:
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Click to expand...
Click to collapse
It's a Linux sh script, so you run it in the Linux terminal. It's the same directions as the other tools, just for Linux
Jhdoubleoseven said:
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
Click to expand...
Click to collapse
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
AceHa92 said:
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
Click to expand...
Click to collapse
The phone takes a moment to reboot into fastboot mode, so the script has it wait for 30 seconds. Can you confirm that still nothing happens after 30 seconds? And the phone does boot into bootloader mode? If so, type
Code:
adb reboot bootloader
fastboot devices
into your terminal and see if it shows up. If it's not showing up you may have a problem with fastboot itself.
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Worked perfectly for my memo pad 7 (176cx) Thank you so much!!
drbobb said:
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Click to expand...
Click to collapse
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Jhdoubleoseven said:
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Click to expand...
Click to collapse
Yep, I think it was OKAY on all commands. I pulled in SuperSU from the store and all root functionality seems okay as well.
I don't understand much of what the script does, especially how
Code:
fastboot flash /system/bin/partlink supersu.tgz
is supposed to work - but then, I haven't looked too closely.
Awesome, really glad it worked out for you! And yeah, I'm not entirely sure -- usually gaining root is based on an exploit so I'd guess that it replaces system binaries with modified ones to allow root access, but haven't rooted many phones so not sure how it generally works. Especially
Code:
fastboot oem start_partitioning
Thanks for this. I tried other one clicks on my fedora 22 box and kept getting fastboot errors. This one worked flawlessly.
Interesting...
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
therealprof said:
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
Click to expand...
Click to collapse
That's not a Zenfone though my friend... this is only for Zenfone 2
Jhdoubleoseven said:
That's not a Zenfone though my friend... this is only for Zenfone 2
Click to expand...
Click to collapse
I know, but at some point I would hope that Asus gets an f'ing clue to develop things once and use that across multiple devices running similar hardware. It's already funny how my ME176C and ME572C run completely different Android implementations (one rootable, the other not) despite being somewhat similar.
It's probably a too obvious question, but as the tutorial is for newbies I feel allowed to do:
Do I need to have an unlocked bootloader to succeed in the rooting ? The reason for asking is that the script successfully restart the phone but then the fastboot commands don't work, I get stuck at "waiting for device".
Thanks.
Outdated security
Hey, your HTTPS certs are out of date. I added a temporary exception, then found the redirect failed. I think you server needs some updating...
Any chance of a mediafire or dropbox link?