Related
Okay I posted this also in the Themes forum for Nexus but I wanted to see if anyone could assist. Someone in the theme forum asked about the bootanimation.zip that shows us the cool animation during boot, while reading this it reminded me of the behold 2. See below
What are the permissions for bootanimation.zip if they were left open to non root then this may-b a way to get root with unlocking the bootloader. This would be the same approach that was used to root the behold 2 where the "try3" file was renamed to play_logo . play_logo then was used to root and after root was opened it would make play_logo_real play which was the boot animation. I may be wrong but couldnt this be a possibility. Thanks, any help is appreciated. Im wondering if Zinx could chime in...
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
seraph1024 said:
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
Click to expand...
Click to collapse
You can always write if I am not mistaken using the low-level write dd if/of command. We would use the bootanimation.zip to run the root command. An example is in the Samsung Behold 2 it was done as follows:
Example
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
This is how it was done. I am wondering if the same can be done on the nexus using bootanimation.zip as it executed at startup. We would basically modify the bootanimation.zip to the above and add a line for it to execute the boot image. By gaining root this way we would still be able to put on a custom recovery and roms without unlocking the bootloader in theroy. The try3 file was created by Zinx and used by Maxisma to bring root to the behold 2. I am pretty sure this may work on the Nexus 1. I hope this helps.
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Okay XDA is back up. Yes I can test. Oh man if this works there will be absolutely no need to unlock the boot loader... Thanks
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Hey Seraph1024 take a look at this. Its too big for XDA so I put it up on pastebin. http://pastebin.com/f62780d32 Its what is contained in the try3 file. Zinx used it in flashrec
No joy.
Code:
$ getprop | grep product.model
[ro.product.model]: [Nexus One]
$ pwd
/data/local
$ ls -al try3
-rwxrwxrwx 1 0 0 74512 Jan 25 13:26 try3
$ id
uid=2000(shell) gid=2000(shell)
$ ./try3 /system/bin/sh
[1] Killed ./try3 /system/bin/sh
$ id
uid=2000(shell) gid=2000(shell)
Exploit does not work.
I was that close to rooting today until i saw this now its made me double think again lol I've been waitin for a custom rom by cyanogen until i rooted, and since its pretty much almost here i was going to root. bah guess i'll wait until CM gets released!
flak0 said:
You can always write if I am not mistaken using the low-level write dd if/of command.
Click to expand...
Click to collapse
You can't on this phone. There are two ARM cores - one running the low-level stuff (bootloader, radio) and the other running Linux.
Without the engineering bootloader (or some exploit) we don't have access to the baseband ARM core, and therefore don't have access to its MMU, which is programmed to deny read/write access to protected areas of the flash - such as the bootloader and splash screens. Even with root, Linux can't access that stuff.
It's going to be really hard to find a kernel exploit for the N1 to get root. Most exploits involve mapping memory to the zero page and then triggering a null pointer de-reference bug in the kernel. But the N1's kernel won't allow such mappings.... I believe the minimum address for mmap on the N1 is around 64k. (It's in the kernel config.)
This is a tough nut to crack.
The behold root was done that way because there's no way to flash the partitons on it.
You still need root in the first place to write to that file. The droid guys have been looking a while for a new root exploit but didnt find one. The problem is that all known exploits have been closed in 2.1.
We need to wait for someone to find a new one that works. Then this would be a real posibility, and there' no need to hijack playlogo.
for what its worth, if you need a lab rat i do not have my phone rooted yet and i am willing to test some things if anyone needs...
i dont plan on rooting it until the ball really gets rolling with everything and until I am 100% satisified with the phones performance
kam187 said:
You still need root in the first place to write to that file.
Click to expand...
Click to collapse
That's what I though. And like it was posted earlier, I don't think there is a exploit since this phone is done differently. I am busy for the next couple of days but if anyone want to "try", I'll make up something but I really doubt any of the old stuff will work on this phone.
Do not use the lagfix anymore voodoo will be incorporated into our new kernels very soon. Thanks
Kept the attachments so you can remove if needed!
I keep getting permission errors when I try this. I found another way to update busybox but the script doesn't work
With the current limited root I have, I could not write to /system/bin. I just woke up and I didn't feel like figuring that out, so I copied stuff to the sdcard, then I used cat to write the file to /system/bin as shown above (steps below). I would suggest before starting, download Quadrant Standard from the Market, run the full benchmark and see where your device is on the list. Mine was below the Galaxy S before starting.
This is what I did (on Mac) to get busybox in place:
Code:
./adb shell
su
mkdir /sdcard/lag_fix/
exit
exit
./adb push ~/Downloads/busybox /sdcard/lag_fix/
./adb shell
su
cat /sdcard/lag_fix/busybox > /system/bin/busybox
cd /system/bin/
chmod 755 busybox
ls -l (check the permissions)
exit
exit
Now busybox is in it's right place with the right permissions.
Now, I have to manually execute the steps in the lagfixme.bat file, because I'm not on a PC and I don't feel like re-writing the script, because I just woke up.
Before pushing the files, I edited lines 35 and 36 in the createlagfix.txt file to fit my sdcard folder path. I like to keep my SD card organized, so I put all the files from the zip into the /sdcard/lag_fix folder I created above. Here is what my line 35 and 36 look like before I push createlagfix.txt to the SD card:
busybox cp /sdcard/lag_fix/playlogos1 /system/bin/playlogos1
busybox cp /sdcard/lag_fix/userinit.sh /system/bin/userinit.sh
Now, I know the folder paths below looks ugly, but that's because I just pushed the files directly from my Downloads folder. Hopefully you guys can see what I did here. If not, let me know and I'll edit the post to read better. These are basically the lines in the batch file written out manually for Mac users:
Code:
./adb kill-server
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/createlagfix.txt /sdcard/lag_fix/createlagfix.sh
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/playlogos1 /sdcard/playlogos1
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/userinit.sh /sdcard/userinit.sh
./adb shell su -c "/system/bin/sh /sdcard/lag_fix/createlagfix.sh"
Once the process is complete, run Quadrant Standard again and you'll see your device as the fastest one in the list.
Many thanks to Dirrk!!
Worked just fine for me.
Thanks for this and your root instructions!
Guys, is the phone actually laggy, or are you just assuming it's laggy because of complaints with the other models? I mean, you've only had them a day or two, right? Took me longer to notice lag than that on my i9000.
I'm tempted to grab a Fascinate, but all the issues I've had with the i9000 and it's a tough call.
I've seen it lag sometimes under high load, but I thought that was normal.
I've tested it with GroceryIQ, to compare against the last 30 seconds or so of this video ( http://www.youtube.com/watch?v=10ox35vMS78 ) and the Fascinate is nowhere near as bad at lagging. That video was 8/21/2010, so they may have updated their application by now, not sure.
Edit - Anyway, it works just fine. Nice work Dirrk! 2,191 !
Yep, worked like a charm! My Quadrant score jumped to 2125 after the fix. Phone is much snappier too. Thanks Dirrk!
i've been trying this but i keep getting permission denied.
can someone take me step by step on how to do this?
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
spotmark said:
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
Click to expand...
Click to collapse
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
m2cool2go said:
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
Click to expand...
Click to collapse
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
C:\sdk\tools>adb shell
$ su
su
# cat /sdcard/busybox > /system/xbin/busybox
cat /sdcard/busybox > /system/xbin/busybox
cannot create /system/xbin/busybox: read-only file system
Any ideas why I'm getting this error? It looks like I'm screwing up something very simple...
namebrandon said:
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
Click to expand...
Click to collapse
Really? I removed Backup Assistant and I'm not bricked. Am I missing something?
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
undo lagfix
Hello. I want to undo this for now, due to running out of space for apps. I assumed running unlagfixme would do the trick, but it hasn't given me back the 1 gb it used. Am I doing it wrong, or is it stuck like this now? Thanks for your help!
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Nevermind, figured it out
xirnibor said:
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Click to expand...
Click to collapse
You screwed up if your only getting 871 thats stock. Open up a shell on your phone and type mount and place the results in here
Whitepaint said:
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
Click to expand...
Click to collapse
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
namebrandon said:
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
Click to expand...
Click to collapse
I am waiting on rom manager so I can make a back up before I continue removing stuff
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here
To start off with: I have an LG Optimus V and am using various forms of CM7 overclocked to a stable 825 mhz.
When I'm using cp to copy files from /sys/devices/platform to my sd-ext partition it errors out saying something like: cp can't stat "insert name here" no such file or directory. Then it just reboots without any warning and is too fast for me to get any more than a glimpse. The code I'm using is:
Code:
cp -aiv /sys/* /sd-ext/sys
Does anyone know of a reason why this might occur? Or better yet, how to fix this? I've heard somewhere that some CM7 kernels don't support loop devices, but that that can be fixed manually. I just don't know how to do it.
If someone knows how to fix this problem please help. Oh yeah, almost forgot... I don't have a computer so please make any help android compatible.
______________
If you've never gone too far, you'll never know how far you can go.
Why are you trying to copy that?
825 stable? Mine freezes above 806
trying to install Debian Linux onto my ext2 partition. I've got it working except for the file transfer, but it doesn't seem to need anything except the /etc files.
Oh and yes 825 stable, very stable. I haven't had any problems until this Debian install. And that only because I haven't even heard of linux until March 2011 and I'm just learning about the interesting stuff, lol
/sys is not just ordinary folder, do "mount -t sysfs sysfs /sd-ext/sys/".
BTW: http://forum.xda-developers.com/showthread.php?t=996746
To the OP:
where'd you find the info to installing debian linux to your ext2? Im interested in doing the same or looking into it
Sent from my LG-P500 using xda premium