Ok so the ubuntu install now works on slide credit goes to eratosthene he updated all the files to make it work all other credit goes to the dev’s listed on the links provided. FYI this was tested on eugenes latest froyo rom.
1. Go to http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/ download the ubuntu.zip file .
2. Unzip to a location on your pc to a folder named ubuntu.
3. Download the ubuntu-slide-v2 from here.
4. Unzip the ubuntu-slide-v2 to the same folder you used in step 2.
5. Create a ubuntu folder on the root of your sdcard .
6. Connect your Slide to the pc verify debugging enabled and storage disabled.
7. Adb push the files in the ubuntu folder to the /sdcard/ubuntu.
8. Then adb shell.
9. cd /sdcard then sh ubuntu.sh
Note: At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
10. sh /data/local/bin/bootubuntu
11. you should now see [email protected]:/#
Note : install completed only do the following if you want to access ubuntu from android vnc app.
12. apt-get update
13. apt-get install tightvncserver
14. export USER=root
15. vncserver -geometry 480x320
16. • Run the android-vnc-viewer app and specify localhost port 5901 .
UPDATE: This is not working on CM 6 , I'm not sure why please help if you know .
That would be sooooo coool
Sent From My HTC Espresso Running Froyo Thanks to eugene373
Tried it but the install fails , may be the script or may be rights to edit the files im not that good with linux yet so im not sure .
Ok thanks, any help would be apriciated . If we can get a procedure that works ill write up a step by step for everyone and maybe make a video how to also.
Just guessing but it's probably because we don't have rw access to /system.
Until we get an unlocked bootloader it ain't happenin...
I could be completely way off though
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
bled82 said:
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
Click to expand...
Click to collapse
An OTA update would unlock it.
So once we get the froyo ota we should be able to follow the same process as the nexus one then ?
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
aceraider4 said:
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
Click to expand...
Click to collapse
Once there is an official OTA devs will be able to extract the keys needed to properly sign files I believe.
I thought the engineering build had an unlocked boot loader on it and once we flashed it that was that ?
Here's an updated zip for you guys. The process is generally the same as on the above-linked nexus one version, I just changed the scripts to move a few files to different places. You'll need to download ubuntu.zip from that post as well. Summary:
unzip ubuntu.zip somewhere
unzip ubuntu-slide.zip in the same place, replace all the files
make a directory called 'ubuntu' on your sdcard
adb push all the files in the zip to that directory
adb shell
cd /sdcard/ubuntu
sh ubuntu.sh
At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
sh /data/local/bin/bootubuntu
You're now chrooted into the ubuntu install. Have fun.
Thanks going to try it now !!!
Does not work get attached error.
bled82 said:
Does not work get attached error.
Click to expand...
Click to collapse
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
falken98 said:
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
Click to expand...
Click to collapse
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
bled82 said:
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
Click to expand...
Click to collapse
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
falken98 said:
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
Click to expand...
Click to collapse
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
bled82 said:
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
Click to expand...
Click to collapse
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
eratosthene said:
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
Click to expand...
Click to collapse
I am running froyo using Kanged CM6 newbuild.zip from eugene373 , http://forum.xda-developers.com/showthread.php?t=721515 .
Related
I've got the HTC Hero from Orange and noticed that the ROM version is higher than the one posted in this forum (Build 1.76.61.3). If somebody could explain how to pull the ROM from the phone I'd be happy to post it.
can u adb into it? if so you just need to type the following in command prompt if your using windows:
adb pull /system
Sweet god you can be a hero if you can use adb and type the following command:
adb pull /proc/config.gz .
and attach the file here!
You can load the 1.3.1 recovery (i think) and nandroid backup the system!
*************THIS IS A GUESS ON HOW TO DO IT!*****************
I bet someone will help you get this dumped!
but you can probably dump the following like so:
adb pull /system ./system (make the folder in your adb directory)
adb pull /data ./data (make the folder in your adb directory)
adb pull /etc ./etc (make the folder in your adb directory)
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
adb pull /sdcard/recovery.img . < there is a . after it and it needs to be there! >
adb pull /sdcard/boot.img . < there is a . after it and it needs to be there! >
This would be my guess on how to do it, but i could be wrong.
I'm downloading the SDK now, will post back if I managed to get anything from the phone.
PS: If I post all those things will any of my personal settings/data be included?
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
herman3101 said:
I've tried all those commands, the only one that worked is the adb pull /system ./system , it didn't work for etc and data, reckoned there weren't any files to copy. the cat... ones just didn't do anything. I'm guessing this is because I'm not rooted on the phone. Any suggestions?
Click to expand...
Click to collapse
System is enough Now please upload it to megaupload/rapidshare
Does system include any user modified files or is it read only during use?
herman3101 said:
Does system include any user modified files or is it read only during use?
Click to expand...
Click to collapse
system is readonly
Excellent, it's still uploading and I will update my other post with the link once it's done. I've also uploaded the config.gz as somebody requested it.
Thank you very much I thing JAC can make a great rom out of this!
upload finished, link on other thread
this thread is done
for more info and the rom look here
http://forum.xda-developers.com/showthread.php?t=540680
Ok so i have looked at all the other posts on how to change the boot screen animation, but none of them seem to work. My phone is running on Android 2.2. Does anybody have any ideas on what i should do?
I JUST did this and it worked for me. I am on the 8/1 2.2 leak as well.
Plug in phone
reboot to recovery
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
It will give you this error. Thats fine (It's just saying it couldnt mount the sdcard which we dont need right now.)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
now type exit to get back to your computer prompt.
Now push your bootanimation.zip you want to /system/customize/resource
Code:
adb push bootanimation.zip /system/customize/resource
now now get back in to adb shell and type
Code:
cd /system/customize/resource
then ls *.zip and it should look like this. l = lowercase L
Code:
/system/customize/resource # ls *.zip
ls *.zip
bootanimation.zip VZW_bootanimation.zip
Now we want to rename the vzw boot animation to .back to save it
Code:
mv VZW_bootanimation.zip VZW_bootanimation.back
Then we want to rename the new bootanimation to the vzw bootanimation
Code:
mv bootanimation.zip VZW_bootanimation.zip
OPTIONAL STEP: IF YOU DONT WANT THE DROID SOUND ON BOOT
Code:
mv Droid.mp3 Droid.back
type exit and adb reboot . It should now boot with your new boot animation.
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Check where I've been posting. Somewhere along the way I was in a thread that worked for me. I just can't remember where.
Utopia73 said:
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Click to expand...
Click to collapse
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
zerf said:
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
Click to expand...
Click to collapse
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Utopia73 said:
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Click to expand...
Click to collapse
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
zerf said:
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
Click to expand...
Click to collapse
Ok did that. Nothing happened
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
zerf said:
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
Click to expand...
Click to collapse
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Utopia73 said:
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Click to expand...
Click to collapse
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
zerf said:
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
Click to expand...
Click to collapse
Well i saw that...maybe its another mount but instead of mounting in prompt i just went to the partitions menu and did it there. Thank you very much!
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Utopia73 said:
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Click to expand...
Click to collapse
where are you seeing this (what directory) and what command are you trying to run?
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
zerf said:
where are you seeing this (what directory) and what command are you trying to run?
Click to expand...
Click to collapse
I was trying to run
Code:
adb push bootanimation.zip /system/customize/resource
Ok, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/customize/resource/bootanimation.zip': No space left on device
So maybe i tried to many times or something.
vbhines said:
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
Click to expand...
Click to collapse
I tried that too, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd
Click to expand...
Click to collapse
I tried that too, now its saying
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Click to expand...
Click to collapse
You have to push it while in Recovery until we have s-off/full NAND. If you're already doing it in Recovery, make sure you've mounted /system first.
Sent from my ADR6300 using XDA App
i have a tmobile g2 and used visionary to root and it did not work right but my s-off and i can not root any way i try,if i have stock rom what do i have to do to reinstall the stom rom and will this make my g2 go back to s-on?
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
renn9420 said:
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
iv tried that and nothing works at all,i was told i needed s-on again because s-off is what i have and no matter what i try i can not root this **** phone!!!!!!im ready to throw it out the window.
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
steviewevie said:
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
Click to expand...
Click to collapse
im about to try it
hightechlive said:
im about to try it
Click to expand...
Click to collapse
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
hightechlive said:
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
Click to expand...
Click to collapse
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
steviewevie said:
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
Click to expand...
Click to collapse
yes i did get forked xxx children message,but i this is different for me
init_module 'wpthis-OTA.ko' failed
i get this
local/tmp/init_module 'wpthis-OTA.ko' failed
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
fastludeh22 said:
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
Click to expand...
Click to collapse
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
hightechlive said:
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
Click to expand...
Click to collapse
*Following instructions in that post includes a wipe. This will delete settings, 3rd party apps, mms etc. Be sure to backup what's needed.
These directions are for windows computers:
Do not unzip the file. It should be clockwork recovery 2.x.x.x.img. just rename it recovery.img. The root of c just means not in any folders. So after naming it recovery.img put it on c. It will then be c:\recovery.img
Then when you open up cmd window, goto sdk folder like when you use adb. With your phone booted into hboot with usb connected. You type this into cmd window: "fastboot flash recovery recovery.img" without the quotes. Then finish following pervious link.
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
i type in command window but it says can not load recovery img
hightechlive said:
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
Click to expand...
Click to collapse
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
fastludeh22 said:
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
Click to expand...
Click to collapse
i type in command window but it says can not load recovery img
im doing everything you said?
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
fastludeh22 said:
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
Click to expand...
Click to collapse
i did that,this i what i did i download and change the name and put the zip file in the c root,open command and went to the tolls folder after the other things to get there in command and this is what it says
says can not load recovery img
What zip file? The recovery should be an img file.
fastludeh22 said:
What zip file? The recovery should be an img file.
Click to expand...
Click to collapse
that what im saying when i down load the file if is zip up and when i unzip it says i can not open it?
when i download it this is the name of the file
recovery-clockwork-2.5.1.2-vision (1)
I went to clockwork thread and clicked link. It dl's as .img file for me. This is the direct link I'm talking about. http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
If your using that, check this. In an open window/folder in windows. Click tools, then folder options. Select view tab. Uncheck "hide extensions of known file types". Then the file extensions should show at the end of every file. Make sure its named right now.
[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.
Reserved
Reserved
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus
Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium
This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk
efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
try /data/local/tmp
Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers
Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
Step 1: Setting up stuff
Find and download a suitable file explorer that allows you to modify and browse system files. I recommend Root Explorer. (Optional)
Download and install Terminal Explorer from the Google Play Store.
Download and install Script Manager from the Google Play Store. (Optional)
Step 2: Walking the path
Open Terminal Emulator and type in
Code:
su
Your root manager should request you for permission. Grant the app superuser permission.
Type in
Code:
vold
Press enter
Type in
Code:
mount -t vfat -o umask:0000,uid=1000,gid=1023 /dev/block/vold/179:33 /storage/sdcard0
Press enter.
Type in
Code:
mount -o bind /data/media /storage/sdcard1
Press enter.
Click to expand...
Click to collapse
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
not work in FW XM Dual
how to swap internal and external in FW XMD ?
@gadgetroid , will it work in Xperia M Dual 4.2 ?
It Worked!!!
gadgetroid said:
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
Click to expand...
Click to collapse
Worked for me
13 GB internal storage
aerialus said:
not work in FW XM Dual
how to swap internal and external in FW XMD ?
Click to expand...
Click to collapse
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Code:
mount > mount
Then, on the computer, open a command prompt window (or terminal on Linux) and type in
Code:
adb pull /partitions
Code:
adb pull /mount
Put these two files in the zip along with the vold folder and post them here. I will look into it and provide you the guide.
jereMarfil24 said:
@gadgetroid , will it work in Xperia M Dual 4.2 ?
Click to expand...
Click to collapse
Since it runs 4.2, I can't be very sure, as Sony may have changed device names. Once the above user submits the files, I will look into it and post the guide.
gadgetroid said:
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Click to expand...
Click to collapse
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Did u written su above?
Sent from my C1904 using Tapatalk 4
aerialus said:
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
gadgetroid said:
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
Click to expand...
Click to collapse
my device is already rooted and have Busybox installed,,
please look at my attachment
aerialus said:
my device is already rooted and have Busybox installed,,
please look at my attachment
Click to expand...
Click to collapse
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
aerialus said:
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
gadgetroid said:
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
Click to expand...
Click to collapse
in XM Dual no need use rootfixer anymore,,
just root with tools and success full root,,
magicw said:
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
Click to expand...
Click to collapse
ok i will try :fingers-crossed:
Yes. That is exactly what it does. It works if you put in sdcard
Script
I have created a script for this. If OP gives me permission i can publish it.
pull partitions and mounts success,,
but when i try to pull folder "/dev/block/vold"
the result is " 0 files pulled, 0 files skipped"
see my attachment
icoolguy1995 said:
I have created a script for this. If OP gives me permission i can publish it.
Click to expand...
Click to collapse
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
gadgetroid said:
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
Click to expand...
Click to collapse
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
icoolguy1995 said:
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
Click to expand...
Click to collapse
I'll add it to the op soon. BTW, if you place the script in /data folder and set it to rw-r--r--, it will be easier. That way, the script won't be in the wrong drive after it's been switched.
No it will not work unless all the options are ticked on permission setting.
icoolguy1995 said:
No it will not work unless all the options are ticked on permission setting.
Click to expand...
Click to collapse
It works for me with rw-r--r--
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.