Related
Has anyone managed to get Debian running on the Hero (as per the instructions in the Dream forum?)
P
I tried but I'm stuck because ext2.ko needs to be compiled for the Hero (managed to boot debian IN recovery mode with the custom image but not under the stock hero cupcake) and I haven't really had the time to look how to do that.
Also, I had hard time installing debian because of weird sh behaviour (looks like it's also cupcake's fault) and needed to modify the install script so it uses busybox tools.
I was getting a fail on the 'modprobe ext2', because of the lack of kernel modules.
Chmod 4755 on the sdcard also fails because of the way it's mounted, you need to run the installer from somewhere else instead.
P
su <installer.sh does work, but sometimes chmod just says "Operation not permitted" and mount fails when using the stock utils on my phone, using busybox seems ok, and I belive that I'm rooted correctly, so I don't know why some chmod fail.
Can ext2.ko be compiled alone or does someone need to rebuild a brand new kernel for the hero ?
ext2, ext3 & other are compiled into the current hero kernel.
Have you tried to compile a kernel from the magic 32a sources that htc released? maybe it boots on hero too (i'll try today, if i have time)?
What does modprobe actually do?
I guess it's important, because when I try and start debian, it all dies horribly and reboots the device.
Not had time or inclination to really investigate yet!
P
modprobe is a wrapper that calls insmod and rmmod(-r option).
modprobe loads a kernel module into the kernel using insmod
In this case, ext2 seems to be needed in order to mount debian.img (looks like it fails there, even if ext2 is compiled into the kernel). No idea about what makes mount fail, but I know that it works in recovery and doesn't in android
If you want to reseach a little about debian on the Hero, I suggest stripping out the reboot line in bootdeb, you will save a lot of time.
No, I didn't try to compile anything for the Hero personally, basically beacuse I have no clue about how to do so (yet)
OK so the normal mount command won't mount debian.img, but 'busybox mount' will.
Woohoo, success!
My doing 'rm /system/bin/mount' this makes 'bootdeb' use the busybox mount instead, and hey presto!
P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll build debian support into the next custom ROM...
P
Here is my installer.sh btw... I copied the debian.img to /sdcard/debian/debian.img but everything else to a new directory called /data/debian. This allows chmod 4755 on the installer.sh file.
I used the 2.1 zip from here.
P
Code:
su <./fsrw
modprobe ext2
clear
rm -f /data/local/bin/fsrw
rm -f /data/local/bin/bootdeb
rm -f /data/local/bin/unionfs
rm -f /data/local/bin/installer.sh
rm -f /data/local/bin/mountonly
mkdir /data/local/mnt
clear
cp -f fsrw /system/bin
cp -f bootdeb /system/bin
cp -f unionfs /system/bin
cp -f installer.sh /system/bin
cp -f mountonly /system/bin
cd /sdcard/debian
chmod 777 *
cd /system/bin/
chmod 4777 *
cd /
clear
echo " "
echo "VERSION 2.1"
echo "Custom Debian Bootloader is now installed! Quick huh?"
echo "This process does NO damage to your Android underlying OS!"
echo " "
echo "Courtesy of http://www.androidfanatic.com"
echo "Installer by Mark Walker (ghostwalker)"
echo " "
echo "To enter the Debian Linux console just type 'bootdeb'"
echo "PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'."
P
modaco said:
Here is my installer.sh btw... I copied the debian.img to /sdcard/debian/debian.img but everything else to a new directory called /data/debian. This allows chmod 4755 on the installer.sh file.
I used the 2.1 zip from here.
P
Code:
...
[b]
cd /system/bin/
chmod 4777 *
[/b]
...
P
Click to expand...
Click to collapse
suid for all /system/bin/ ????
That's from the standard provided installer.sh script.
I don't see any issue or danger with that tho? If you prefer you could do just do the files individually.
P
well... with
Code:
cd /system/bin/
chmod 4777 *
every executable on /system/bin will be executed with the permissions of the executable's owner, and everyone have rwx access to every single binary in /system/bin
What exactly can you do with Debian?
You sohuld be able to do anything on your phone you can do with a full debian distro.
Shame there's no hero with a hardware keyboard tho!
P
modaco said:
You sohuld be able to do anything on your phone you can do with a full debian distro.
Shame there's no hero with a hardware keyboard tho!
P
Click to expand...
Click to collapse
Yeah I figured that out lol, but what can you do with a debian distro?
Still fails here, no idea about what to do.
# busybox mount -o loop,noatime /sdcard/debian/debian.img /data/local/mnt
mount: mounting /sdcard/debian/debian.img on /data/local/mnt failed: No such file or directory
/sdcard/debian/debian.img and /data/local/mnt both exist, and this line works in recovery
Any idea ?
EDIT : Fixed it !
In bootdeb, I needed to replace "mknod /dev/loop2 b 7 0" with "mknod /dev/loop0 b 7 0"
Maybe I'll rebuild a debian zip ready for the hero with a proper install script, or even as an update.zip when I'll look into android customisation
BTW (offtopic) : I'm also really intrested in a stock android (like Cyanogen roms for the G1) with mods for the Hero (with Flac patches for example), and maybe donut ! I'll be glad to help if you need.
EDIT 2 : Also, I don't really like how the script is done. In a world of android multitasting, we only can run one debian shell at the time ?
My idea is easy to do (I think) :
- Don't make bootdeb run chroot directly
- Make a debshell script that will launch a debian shell
- Make a debshutdown script that shuts down debian and doesn't reboot the phone if you throw it arguments.
OR : Make a big debian script that parses the command line and do what the 3 different scripts do, and do like the classic bootdeb if no argument is providen
I hope I explained what I think well
I DIDN'T need to do that, how weird!
P
Why Debian?
Why would we wan't to run Debian(=linux) when we have android(=linux)??
I'm also a bit worried about the permissions in /system/bin.. This means that everyone can make changes to every binary that Android has..
Virusses are not yet in the open, but you really make it very easy to exploit your phone (imagine a virus which acts as a dialer!!)
[ info ]
i am attaching a easy to run package which contains the files required for full functionality of executing startup scripts (init.d scripts)...
basically this will allow the user to execute custom shell scripts, placed in /system/etc/init.d/ folder and they will be executed on each boot!
i dont have this device yet!!
thanks to Jozinek for testing this on his phone!
[ requirements ]
stock rooted ROM
windows PC with adb drivers installed
[ how to install ]
download the provided zip package
save it on c:\
extract the contents of the package
connect phone with usb debugging active to PC via ADB
execute "runme.bat"
follow onscreen instructions & enjoy!
incase some issue is there post the output/log of script
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
[ donations/device fund ]
i dont yet have this device but i plan to buy it.... if u guys want to donate to me to get this device OR if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
i am currently channeling all my donations to get this phone asap and to avoid selling my ARC!!!
PAYPAL DONATION LINK
[ download link ]
generic-init.d-support-v01.zip
MD5HASH: 2eda273af4b91c34f868807820cceaee
let me know how it goes!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENJOY!
Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc
somemadcaaant said:
Nice work, this will enable the Speedy v7 int.d hacks, can you incorporate this in the above? As an addon perhaps.
Done, $50 "AU" dollars coming your way mate.
-smc
Click to expand...
Click to collapse
this init.d support can be used to execute ANY shell script/program at startup... u are free to choose the ones u want...
if anyone needs help on how to push the scripts onto device let me know... but script specific info i dont have, u will need to ask the developer of those scripts..
I used this script to move dalvik cache to /cache folder:
Code:
#!/system/bin/sh
#
# relocate dalvik-cache to /cache/dalvik-cache
if [ ! -d /cache/dalvik-cache ]
then
busybox rm -rf /cache/dalvik-cache /data/dalvik-cache
mkdir /cache/dalvik-cache /data/dalvik-cache
fi
busybox chown 1000:1000 /cache/dalvik-cache
busybox chmod 0771 /cache/dalvik-cache
# create symlink
busybox mount -o bind /cache/dalvik-cache /data/dalvik-cache
busybox chown 1000:1000 /data/dalvik-cache
busybox chmod 0771 /data/dalvik-cache
After reboot i saw folder /cache-dalvid in both folders /data and /cache, is it normal?
Thank!
I found that for devices rooted with locked bootloader
Line 21 of runme.bat need to change from
HTML:
@files\adb shell "su -c 'busybox mount -t ext4 -o rw,remount /system /system'"
to
HTML:
@files\adb shell "su -c 'busybox mount -o remount,rw /system'"
This is all great, exactly what I was looking for! But what about if the ROM already has a custom kernel that makes use of /etc/init.d? Do the /etc/init.d scripts get executed twice?
EDIT: in my phone this solution can't work. In the init.rc file the following lines are commented out
Code:
#service flash_recovery /system/etc/install-recovery.sh
# oneshot
Thanks, it's working but I have a question, how we can include this in a rom?
Please respond, I would appreciate that
DooMLoRD said:
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
Click to expand...
Click to collapse
That means I don't need run-parts if I've busybox installed?
1-Tell me please if I understand: I've done everything the post says Doomlord ([ADDON] [Xperia S] Generic startup /init.d scripts support for Stock ROM / Kernel) my question is this, after this I can already install scripts from cwm?
2-I try installing ''NullVoid'' tweaK by cmw and apparently well was installed. (I say apparently because i do not know if it is working)
3-Another thing about Tweaks: These have to be installed every time the phone restarts? This tweaks are compatible with the stock ics rom? (With the Doomloard Method ?
DooMLoRD said:
........
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
..........
Click to expand...
Click to collapse
So the "install-recovery.sh" file is executed by system by default and does not need to be executed manually from terminal or what else?
And about the file...that is not a one-run file...right? It is executed at every phone boot...right??
Thank you.
Sent from my GT-I9000 using xda app-developers app
AW: [ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel
Sorry leaving footprint, to see this again after im home.
Gesendet von meinem LT26i mit Tapatalk 2
Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you
marvasten said:
Hello,
Is this package valid for deodexed rom?
I'm on stock .55, bootloader locked.
Currently the folder /system/etc/init.d doesn't exists
Thank you
Click to expand...
Click to collapse
it doesnt matter which ROM you are on... this should work on any ROM as long as the kernel ramdisk executes install-recovery.sh service...
dont worry it creates all required folders/files
I only have the NEW Nexus 7 and Nexus 4, so I am relying on you all to test...
Although it should work swimmingly!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make Your Nexus Perfect
WHAT'S NEW?
> VER 1.5 | SEPT 10 2013
-> Quick Install quickened to 4 clicks as opposed to 6
-> Backup/Restore Menu Added
-> Backup/Restore User Apps and be able to remove backups
-> Backup/Restore Anything using keep.txt and be able to remove backups
-> How To section updated with info on Backup/Restore Menu
-> junk.txt Updated with Media and Face Unlock files
-> On the horizon: App deletion in AROMA installer
PREREQS
Nexus Device that has a system app you do not want
Grade school diploma (i.e. ability to read)
THE SKINNY
WHAT IS NIGHTLY UPDATER
Nightly Updater is an AROMA installer for those that
yearn to have the cleanest device. Since I first
owned an HTC Droid Eris, I have been wiping bloatware
off of my device. Flash foward to my latest devices -
LG Nexus 4 and the 2013 Asus Nexus 7 and there ain't
much bloatware... But, all AOSP ROMs tend to come with
at least one or two apps that I can do without (and
sometimes a lot more). Nightly Updater is a simple
tool that allows users to remove unwanted system
applications in an easy manner. NU also allows users
to customize which apps are removed.
HOW DOES IT WORK
Nightly Updater works by relying on scripts that
read txt files. When customizing your script, the
installer looks for junk.txt in the "NU" folder of
your virtual (i.e. internal) SD card. Each line that
has not been "commented out" (i.e. does not have a
"#" at the front of it) or any terms (i.e. app
descriptions) that follow a "#" are removed from the
script. This leaves Nightly Updater with a clean text
file that only has the applications you want to remove.
Review:
Custom Script is called: junk.txt
Custom Script goes here: /sdcard/NU/junk.txt
#Chrome.apk -- NOT DELETED FROM DEVICE
Chrome.apk -- DELETED FROM DEVICE
Chrome.apk #Google Browser -- AFTER "#" IGNORED
HOW DO I ADD MY OWN APPS
You can add your own apps in three ways: [1] name (without
apk), [2] name (with apk), or [3] file path.
[1] Name (without ".apk")... Just type:
Code:
Chrome
The installer will automatically know it is looking for an apk and
delete Chrome.apk.
[2] Name (with ".apk")... Just type:
Code:
Chrome.apk
I think you know what it does.
[3] Full File Path... Now, you can get a little funkier and do the entire
file path like:
Code:
/data/app/Chrome.apk
This comes in
handy for files like pre-loaded wallpapers and
ringtones you may want to remove. Be cognizant of
where the files you are removing are located! This
will become very important when telling Nightly
Updater where to scan.
By the way, Nightly Updater also recognizes wildcards.
This is great for those user apps that end up having
unpredictable file names. For example:
Code:
/data/app/com.google.android.youtub*.apk
com.google.android.youtube*
These are both ways of erasing YouTube regardless of
the "-X" at the end of the file name.
WHAT'S UP WITH SCANNING
When using a Custom Script, Nightly Updater asks
where you would like to scan for apps. By default,
Nightly Updater recommends you only scan in the
System/App folder - which is where (shocker) system
apps are located. Remember, most junk apps are located
in System/App. However, Nightly Updater has also given
the option to scan Data/App. Some developers will put
apps in the Data/App folder, so it may be useful to
remove apps from there. But NORMALLY, these are only
the apps you chose to install. The final option is
to scan EVERYWHERE. Be very cautious with this command!
Remember that it is matching what you write in
junk.txt with the scan parameter. If you accidentally
wrote "system" as an app you wanted to remove instead
of SystemTuner.apk (with full scan on)... you would
erase your system folder... that's REALLY BAD!!!
Now, if you only check this option when you are using
full path and double check your junk.txt file so that
you did not make any mistakes... YOU ARE GOOD!!!
When in doubt, post your junk.txt here and I will
check it over for you
WHAT'S THE DEFAULT SCRIPT
If you download junk.txt from the OP at XDA, then
you have seen the Default Script. The Default
Script is meant to remove apps that MOST people
would consider expendable. If you are nervous to
tinker with your own Custom Script, try running
the Default Script first. If the script deleted
an app you need or did not delete at app you want
to destroy - hit me up and I will walk you
through the steps.
MORE DIRECTIONS ARE IN THE INSTALLER
DOWNLOADS
Check the "Downloads" Tab
NU-1.5.zip - Nightly Updater Installer
junk.txt - Customizable Removal Script
keep.txt - Customizable Backup Script
BUGS
Installer will occasionally hang when you press "< Back" - Reboot Device to fix temporarily
You tell me
HOW YOU CAN HELP
Give me feature ideas
Come up with more pre-loaded apps to be added to junk.txt
SPECIAL THANKS
Patrics83 and the whole ROM Cleaner team for the inspiration of this amazing tool!!! :good:
XDA:DevDB Information
Nightly Updater, a Tool/Utility for the Google Nexus 10
Contributors
swagstr
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2013-09-10
Created 2013-09-09
Last Updated 2013-09-10
This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk
sttovo said:
This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk
Click to expand...
Click to collapse
Most definitely works with system apps. Just add "Apollo" and scan system... /system/app/Apollo.apk is deleted! I really like your script too! Smart idea to back up init.d and boot animation!
Sent from my Nexus 4 using Tapatalk 4
swagstr said:
I really like your script too! Smart idea to back up init.d and boot animation!
Click to expand...
Click to collapse
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!
sttovo said:
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!
Click to expand...
Click to collapse
Good to hear! :good:
Also, if any of you adventurous five people out there that downloaded this bad boy want to post some results for the Manta... that would be nice (As I do not have one)
Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"
sttovo said:
Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"
Click to expand...
Click to collapse
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4
swagstr said:
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Sorry, it only does rm -f currently. So for now add the "*" and it will delete everything in the folder for ya! If it doesn't break anything I will add the recursive command for folders.
Hey y'all! Working on a sizable update that is trying include several things requested from different devices. Looking for a little help on the testing side. First few that hit me up will get it.
Sent from my Nexus 4 using Tapatalk 4
BIG WARNING! DO NOT use the Data Wipe in version 1.5 and below. The script does not exclude the "media" folder... As some of you know... That's the SD CARD! I just did it and it SUCKED lol It will be fixed in the next version along with many new updates
Sent from my Nexus 4 using Tapatalk 4
Yo. Working diligently on the backup/restore feature. Next update will be sick. Standby
Sent from my Nexus 4 using Tapatalk 4
I removed download link due to this method not working on lollipop.
This guide is deprecated, please use TWRP Recovery from this thread to install root
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
You have been warned!
Links:
Sony PC Companion
Download link removed while I will test for compatibility with 5.x, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reserved
How it works:
1. Each boot.img packs zImage (real kernel) and ramdisk (special files for kernel use)
2. This one has all modifications from LGGW rootboot by Justin Case:
a. Adds su binary, superuser.sh install script, modified install-recovery.sh and additional step into init.rc file to invoke superuser.sh install script. Also modifications to mount system as rw and some disabled security.
3. So basically it mount system as rw and does following (cut from superuser.sh install script):
Code:
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/sleep 2
/system/bin/cat /sbin/su > /system/xbin/su
/system/bin/cat /sbin/su > /system/xbin/daemonsu
/system/bin/cat /sbin/install-recovery.sh > /system/etc/install-recovery.sh
/system/bin/chown 0.0 /system/xbin/su
/system/bin/chown 0.0 /system/xbin/daemonsu
/system/bin/chown 0.0 /system/etc/install-recovery.sh
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu
/system/bin/chmod 755 /system/etc/install-recovery.sh
/system/bin/sync
/system/bin/sleep 3
/system/bin/reboot
I have dumped the rom from my debug/test version and was wondering if you were able to give me a guide on how i could try and flash it with a retail version? I presume this root guide probably won't work for me
Well, if hardware and partitions are the same - I do not see why it will not work. However, it will not help to flash.
I might try to compile twrp, but will have to carefully read its docs first.
thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?
iBuzman said:
thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?
Click to expand...
Click to collapse
Thanks for letting me know!
I reverse engineered changes in LGGW by unpacking and comparing ramdisks from both rootboot and original lg kernel and then applied the same changes to our kernel extracted from PC Companion files.
great thinking and good job ?
btw, that pic confirmed su access to watch over bluetooth debug connection ?
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.
Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
how to benefit?
root apps of course!!
(sry for bad pic, unlocked bootloader z3 in low light [emoji12]
XorZone said:
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.
Click to expand...
Click to collapse
that's awesome man! will purchase mine next week, can't wait to root it. thanks for the answer.
Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.
cb22 said:
Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.
Click to expand...
Click to collapse
Yeah, I noticed the same about WiFi chip, it might be that they packed bcm43341 as part of the BCM23550 soc, like Invensense MPU9250 chip packs mpu6500 inside.
For the 43341 I'm finding it in the configs here: https://android.googlesource.com/kernel/tegra/+/bdde9f16131a5ac2039062d5ce22e3e153acbe68^!/
Looks like BCM43341 is BCM4334 + NFC chip, so we could try S3 I9300 files as per http://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9300Firmwares
how can i grant superuser permission to an app? i install es file explorer with sideload but i can't get superuser permission. the procedure is ok
Sorry admins for not putting in correct location....
Moved to Correct Area!
cdrshm said:
Sorry admins for not putting in correct location....
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Click to expand...
Click to collapse
As usual, check if adb enabled in settings-about-developer options, if there are no developer options - it is as usual 7 times click on build number in about screen.
And please use Q&A thread for such questions
I've confirmed root survives the Lollipop update
Wow, I was out whole weekend, will have to catch up with the update
Root section #Hello guys,
after 45564564165 hours of research (joke but this took me about 1 week ._.) I finally rooted Project Astoria
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current issuesApps can't request root because of limit of project astoria. I'm working on it.
ProcedurePerform an Hard reset first.
After settings up, deploy Root Tool.
Go to Lumia Registry Editor, click on navbar > templates and then select all.
Close the app and go to settings > Update and security > For developers.
Enable developer mode and click on Discovery. It should show to you the pin.
Download Astoria Tools.rar
Extract it.
Open that extracted folder.
You should see wconnect and so on.
On the "void" area, make SHIFT + Right click, and then click to "Open Command prompts here".
Write wconnect usb and write the pin.
After this, download AOW shortcut.7z in the attachment, extract it, copy that in your phone, example "Phone\Documents"
Now, go to your phone and open File Explorer. Open Documents and click on Aow shortcut
Go to RootFS directory and delete the file init.
Warning, there are 2 files, you need to delete "init.rc", it has about 20-19 KB.
Restart now your phone.
Keep it plugged on computer and wait about 5 minutes. it should you show "Windows Phone" device connection.
Open it and go to: Data\Users\DefApps\APPDATA\Local\Aow\RootFS
Download from Astoria folder link, the latest Rootkit & Gapps version.
Extract it.
Copy ALL Files to the phone (Data\Users\DefApps\APPDATA\Local\Aow\RootFS).
It ask you if you want to replace/merge files. Say Yes.
Press yes if it show this to you:
After you finished you need to set MTP to the standard path.
Download CustomPFD and deploy it.
Open that app.
Navigate to TWEAKS PAGE and click to General tweaks.
Navigate to UTILITIES: check FULL FS ACCESS and uncheck again.
Restart your phone.
Download Superuser.rar and extract it on Astoria tools folder.
After boot, connect to your pc and install superuser.apk (adb install superuser.apk)
After installation, you can launch the command "adb shell" and as you can see you are a root user
I'm really destroyed but at the same time happy
THANKSdjamol and ngame for his Interop Unlock method/app.
Marocco2 for his help.
snickler for his help.
Pasqui industry for making CustomPFD.
(I forgot someone?)
And all member of XDA and the world itself
Download
Astoria Folder (Astoria Tools - AOW shortcut - Rootkit & gapps): http://astoriafolder.adeltax.com (Redirect to mediafire)
Attached some files because of problem with mediafire (stupid block)
-- EDIT --
If you have problem with installing APK after root, go to your phone and delete packageinstaller.odex using Aow shortcut and going to RootFS > System > app folder (The lowest size, approx 153 KB)
GAPPS Section
Not yet, still working on it.
Here will be my "research"
Changelog:
v0.72
First version.
I will make GUI Installer/Package manager or something like this.
You are a monster, on fire!
\o/.
U are my hero o/
Happy rooting
Ah so you actually have to delete the init.rc files and wait for them to reproduce? That's why! Awesome job. I can't wait to test this out @ADeltaX
Hello there,
I can then the Google Play Store etc. properly use and also
Install Android applications on the Store from Google?
HannHenne said:
Hello there,
I can then the Google Play Store etc. properly use and also
Install Android applications on the Store from Google?
Click to expand...
Click to collapse
Not yet. For now it's very hard to resolve an "issue".
@ADeltaX, have you tried Insecure root or insecure su binary? The su binary that doesn't rely on a root management app like SuperSU? Because we can get direct root access on an app instantly if it requests for root with that...
Sent from Ponyville
Can we get a custom android with root now?
Got to final Stage now im getting an error code 14 Problem booting Astoria
Using Lumia Icon (929) on OS 10166
Lanex777 said:
Can we get a custom android with root now?
Click to expand...
Click to collapse
Nope, you need to edit Hyper-v library (and this is impossible)
darkcroc said:
Got to final Stage now im getting an error code 14 Problem booting Astoria
Using Lumia Icon (929) on OS 10166
Click to expand...
Click to collapse
Some files are missing on AOW folder.
Retry and replace the folder again.
mrchezco1995 said:
@ADeltaX, have you tried Insecure root or insecure su binary? The su binary that doesn't rely on a root management app like SuperSU? Because we can get direct root access on an app instantly if it requests for root with that...
Sent from Ponyville
Click to expand...
Click to collapse
Nope, Sincerely I never heard about insecure SU binary.
The SU version is a modded one, because if I use the SuperSU version, on invoking SU it say "segmentation fault" --> mean something doesn't work like shared object (library aka .so).
Someone can compile strace binary for armeabi/armeabi-v7a?
At this time Virtual Box doesn't want to start (I have Linux Mint in VM with AOSP source).
ADeltaX said:
Nope, Sincerely I never heard about insecure SU binary.
The SU version is a modded one, because if I use the SuperSU version, on invoking SU it say "segmentation fault" --> mean something doesn't work like shared object (library aka .so).
Click to expand...
Click to collapse
Some Chinese tablets I fix had insecure su... How did I know? When I adb shell it's already # . Or those only work with adb and not apps requiring su permission?
Sent from Ponyville