Database Info

[DUMP] Sidekick 4G Partition + Kernel Source (Bootloader, Recovery, etc)

Credit to sofauxboho for performing dumps.
Partition Dump
http://gititbit.ch/sk4g2 - partition dump
Code:
bml1 256 KB contains boot.bin (262144 bytes), Primary Boot Loader (low-level hardware initialization)
bml2 256 KB contains PIT file first 512 bytes
bml3 10240 KB /dev/block/stl3 /efs
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml6 5120 KB param.lfs /mnt/.lfs j4fs
bml7 7680 KB contains zImage and initramfs
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
bml9 293376 KB factoryfs.rfs ( /system RFS Partition) /dev/block/stl9
bml10 137216 KB dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
bml11 35840 KB cache.rfs ( /cache RFS Partition) /dev/block/stl11
bml12 12800 KB modem.bin
EDIT: It has come to my attention that the Super One Click works, no need for a script.
More Mirrors
http://gititbit.ch/sk41 - Sidekick 4G system dump
http://gititbit.ch/sk4g1 - Sidekick 4G Info Dump
dev.txt
devblock.txt
efs.txt
mount.txt
partitions.txt
proc.txt
Kernel + Platform Source
http://gititbit.ch/sk4g5 - SGH-T839_OpenSource.zip
Now for custom roms...
SK4G development chat can be found at irc.freenode.net #sk4g

hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.

Use winrar to extract the .rar then place the extracted folder onto the sdcard.

dasmoover said:
Use winrar to extract the .rar then place the extracted folder onto the sdcard.
Click to expand...
Click to collapse
ok, think i did that, but am still getting 'operation not permitted'..... perhaps i'll hold off and see if someone else has success with it?

Hmm...
Should line 14 specify the su file rather than the containing directory?
It currently reads:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/
But perhaps it should read:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/su

Updated the script in the main download.

yogi2010 said:
hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.
Click to expand...
Click to collapse
Im getting this when I try the lines too.

When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.

Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
No I was usin the old link didn't try new one yet. Still says same thing on new version
Sent From SK4G

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
I tried the newer download. All of the chmods error because my user doesn't own those files or already have write permissions for any of them. I don't have read, write, or execute permissions for /data/local/tmp either, so I can't list or copy to that location. But, separate from that, there is no cp command, so I can't copy anything anywhere.

jarrodlombardo said:
When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.
Click to expand...
Click to collapse
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.

sofauxboho said:
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.
Click to expand...
Click to collapse
Type this into terminal right?

Actually, I whipped up a modified version of dasmoover's tool with my changes:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip that and copy the "autoroot" folder to your SD card.
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer.
Then follow dasmoover's instructions (I've cleaned them up slightlly):
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
chmod 755 /sdcard/autoroot/autoroot.sh
./sdcard/autoroot/autoroot.sh
If the sdcard is mounted as noexec, follow these steps:
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
cat > /sdcard/autoroot/autoroot.sh /data/local/tmp/autoroot.sh
chmod 755 /data/local/tmp/autoroot.sh
cd /sdcard/autoroot/
./data/local/tmp/autoroot.sh
Click to expand...
Click to collapse
All credit to dasmoover, btw! Thanks, and I hope you don't mind me modifying and repackaging your tool. Just trying to help get it working.

BTW, here are some good goodies on how this root exploit works for the technical and curious:
I'd read this one first: http://intrepidusgroup.com/insight/2010/09/android-root-source-code-looking-at-the-c-skills/
And this one second:
http://dtors.org/2010/08/25/reversing-latest-exploid-release/

How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G

I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)

Ace42 said:
How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G
Click to expand...
Click to collapse
So, the # means root. The $ means not root. The whole point of this is to get the #, which indicates a root prompt.
If it says the directory can't be found then either the command was typed incorrectly or the files are in the wrong place. The files have to be in the exact right places with the exact right names.
Download my modified version:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip it, and it should give you a folder called "autoroot". Inside that should be four files:
autoroot.sh
rageagainstthecage-arm5.bin
su
Superuser.apk
Make sure there is only a folder named "autoroot" with those four files inside. If there is another directory inside it won't work. If the names are at all different it won't work.
Copy this "autoroot" folder to the top level of your SD card. There should be other folders there like Music, DCIM, Playlists, and Android. Maybe some others. Make sure it's at the very top level, along with these other directories.
Here, take a look at my directory structure:
{
"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"
}
(Yes, I'm on a Mac, but your SK and Android don't care. File locations work the same on Windows or Linux or whatever. Also, I may have some folders you don't have. That's ok.)
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer. **I forgot this part earlier! It's important.**
Then open up Terminal Emulator an your SK4G. Type:
Code:
cd /sdcard/autoroot
Then type:
Code:
ls
This should list the same four files above. If it does, you're ready to start the instructions I posted previously.
If it doesn't, type:
Then type:
Code:
ls /sdcard/
Let me know what it says.

jarrodlombardo said:
I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)
Click to expand...
Click to collapse
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
(To confirm, you can still root by using adb to manually put these files at /data/local/tmp/ For some reason, adb has rights to this location. However, the standard Terminal Emulator does not. This is only a hang-up for on-device rooting, not rooting in general.)

sofauxboho said:
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
Click to expand...
Click to collapse
I've poked around some and not found anywhere yet. :/

[TOOL] ModYourROM LITE (remove bloat & add apps after flashing)

Hey! ^_^
I made a script to remove the bloat from ROMs, add some script functionality and replace some system APKs. It's simple, but really powerful. I use it everytime I get a new ROM because I like plain stock ROMs, with only the system apps. I dunno, I just like it that way .
So, here it is, ModYourROM LITE! ^^!. It’s intended to be used AFTER A ROM FLASH, INSIDE RECOVERY, AND BEFORE THE FIRST BOOT, but it can run afterwards with no issues, I guess.
ROM Compatibility? for now, it’s been tested only with GingerYoshi 1.1 and 1.2 (awesome ROM by the way ).
Now…
Very Important Notes, or V.I.N. for short. Yeah, like Vin Diesel, only that he’ll come and punch you right in your face if you don’t read AND follow them =P.
You need to have ADB in your PATH variable, or edit the script accordingly (!!!).
This script is made for Linux. If you’re on Windows, replace "#" by "REM" and remove the first line of the script.
Don’t just bluntly run it. READ what the script does before running it. It’s common-linux-sense.
You need to have busybox run-parts on your ROM for the startup-scripts functionality. GingerYoshi has it, I don't know which other ROMs have it. It's only needed if you want the startup scripts though.
This script creates a folder called “bak” in your SD card, in case you want to redo the changes. Be sure to have it inserted on the phone before running the script.
Last but not least: I’m not responsible if this breaks your phone, ROM, flying toaster or BORGizes your phone and assimilates you. This script has been working on my phone & setup without much modifications other than adding/removing a few APKs or scripts, so this is the only guarantee I give you. It hasn’t broken mine, but YDMV (Your Device May Vary). Still, you can PM me or post here and I'll try to help you fix something this script has made. However, I'm no expert so I may - or may not - fix what this script did on your phone.
Now, let’s get our hands dirty:
Create a folder somewhere (ie Destkop). I’ll call it “myr“.
Add your custom APKs into myr/apks. Rename them if needed so they have simple names with no spaces. Stuff like foo.bar.boo.hoo.apk sucks =P.
Add your startup scripts (if any) into myr/scripts (you can find some at the bottom of this post).
Add your boot animation replacement (if any) into myr/boot.
Add the latest busybox for ARM5 (in the case of HTC Magic, busybox-armv5l) into myr/busybox. You can find it HERE. Rename it as busy1184, WITH NO EXTENSION.
Put the following scripts in your myr folder:
myrLITE.sh
Code:
#!/bin/sh
# ================================================================================================================
# ModYourROM LITE v1.1 by DARKGuy (dark DOT guy DOT 2008 AT gmail DOT com)
# 6th Jun 2011
#
# WINDOWS USER: Replace # by REM and delete the first line. Be sure to have adb in your PATH environment variable.
# ================================================================================================================
# =====================================================================
# DO NOT REMOVE THIS ADB SEGMENT
# =====================================================================
echo "Mounting..."
adb -d shell mount /data
adb -d shell mount /system
adb -d shell mount /sdcard
adb -d shell mount /sd-ext
adb -d shell mkdir /sdcard/bak
# =====================================================================
# Remove this segment if you don't want to update busybox
# =====================================================================
adb -d push busybox/busybox1184 /sdcard/busy1184
adb -d shell dd if=/sdcard/busy1184 of=/system/bin/busybox
adb -d shell chmod 755 /system/bin/busybox
adb -d shell /system/bin/busybox --install /system/xbin
adb -d shell rm /sdcard/busy1184
# =====================================================================
# Remove these two segments if you don't want/have any startup scripts
# =====================================================================
echo "Adding startup script functionality..."
adb -d shell mkdir /data/local/scripts
adb -d push 90scripts.sh /system/etc/init.d/90scripts
adb -d shell chmod 0750 /system/etc/init.d/90scripts
adb -d shell chown 0:2000 /system/etc/init.d/90scripts
echo "Adding startup scripts..."
adb -d push scripts/noatime.sh /data/local/scripts/noatime.sh
adb -d push scripts/autokiller.sh /data/local/scripts/autokiller.sh
adb -d push scripts/non-rotational.sh /data/local/scripts/non-rotational.sh
adb -d shell chmod +x /data/local/scripts/noatime.sh
adb -d shell chmod +x /data/local/scripts/autokiller.sh
adb -d shell chmod +x /data/local/scripts/non-rotational.sh
# =====================================================================
# Take a look at what apps does this segment remove and delete the
# lines of apps you want to KEEP on your device.
# =====================================================================
echo "Removing apps..."
# Safe to remove
adb -d shell mv /system/app/Protips.apk /sdcard/bak
adb -d shell mv /system/app/PicoTts.apk /sdcard/bak
adb -d shell mv /system/app/TtsService.apk /sdcard/bak
adb -d shell mv /system/app/VoiceDialer.apk /sdcard/bak
adb -d shell mv /system/app/GoogleBackupTransport.apk /sdcard/bak
adb -d shell mv /system/app/GoogleFeedback.apk /sdcard/bak
adb -d shell mv /system/app/GooglePartnerSetup.apk /sdcard/bak
adb -d shell mv /system/app/OneTimeInitializer.apk /sdcard/bak
adb -d shell mv /system/app/ApplicationsProvider.apk /sdcard/bak
adb -d shell mv /system/app/Development.apk /sdcard/bak
adb -d shell mv /system/app/Stk.apk /sdcard/bak
# Bloat
adb -d shell mv /data/app/YouTube.apk /sdcard/bak
adb -d shell mv /data/app/DSPManager.apk /sdcard/bak
adb -d shell mv /system/app/Maxthon.apk /sdcard/bak
adb -d shell mv /system/app/GoogleQuickSearchBox.apk /sdcard/bak
adb -d shell mv /system/app/ThemeChooser.apk /sdcard/bak
adb -d shell mv /system/app/ThemeManager.apk /sdcard/bak
adb -d shell mv /system/app/lindamanager.apk /sdcard/bak
# Core app (I don't use GTalk. Delete if you do).
adb -d shell mv /system/app/Talk.apk /sdcard/bak
# Core app (I don't use the News Reader. Delete if you do).
adb -d shell mv /system/app/GenieWidget.apk /sdcard/bak
# Core app (I don't use the Email app. Delete if you do).
adb -d shell mv /system/app/Email.apk /sdcard/bak
# To be replaced afterwards (READ NOTE IN NEXT SEGMENT)
adb -d shell mv /system/app/DeskClock.apk /sdcard/bak
adb -d shell mv /system/app/Gallery3D.apk /sdcard/bak
# Remove launchers, so we add our own later (READ NOTE IN NEXT SEGMENT)
adb -d shell mv /system/app/Launcher2.apk /sdcard/bak
adb -d shell mv /system/app/ZeamLauncher.apk /sdcard/bak
# =====================================================================
# Remove this segment if you don't want/have any bootanimation.zip
# =====================================================================
echo "Changing boot animation..."
adb -d shell rm -f /system/media/bootanimation.zip
adb -d push boot/bootanimation.zip /system/media/bootanimation.zip
# =====================================================================
# Remove this segment if you don't want/have any replacement apps.
#
# BE SURE TO HAVE A REPLACEMENT APP HERE IN CASE YOU REMOVE CORE APPS,
# like the Clock, News Reader (GenieWidget), Email, Launcher and Gallery3D (which are
# removed above if you didn't look carefully enough - and as for Gallery, I replace it with a
# faster, maybe-not-so-eyecandy-er 2D one).
# =====================================================================
echo "Adding replacement apps..."
adb -d push apks/AlarmClockPlus.apk /system/app/AlarmClockPlus.apk
adb -d push apks/Gallery.apk /system/app/Gallery.apk
adb -d push apks/LauncherPro.apk /system/app/LauncherPro.apk
# =====================================================================
# Don't delete this, it's safe to keep it. Your next boot will be a bit
# slower because it's regenerating the odex files.
# =====================================================================
echo "Cleaning dalvik-cache..."
adb -d shell rm -f /data/dalvik-cache/*
adb -d shell rm -f /sd-ext/dalvik-cache/*
adb -d shell busybox sync
echo "."
echo "Done! Enjoy your new LITE ROM :)"
echo "Script by DARKGuy"
echo "http://www.drakkengard.com/blog/"
echo "."
90scripts
Code:
#!/system/bin/sh
sList=`ls /data/local/scripts/*.sh`
for myScript in $sList
do
sh $myScript
done
Now, EDIT ACCORDINGLY BEFORE RUNNING the myrLITE script.
You should end up with something like this:
{
"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"
}
Now, if you’re on Linux, run this first:
Code:
chmod +x myrLITE.sh
Then run the script:
Code:
./myrLITE.sh
If you’re on Windows, just name it myrLITE.bat and run it from a command prompt.
Now just plain enjoy your new LITE’d ROM .
Credits and references:
* GingerYoshi by Yoshi Team ( here ).
* SD Tweakz by Ungaze ( here and here ).
* Some theory on removing some APKs and autokiller script by tom0769 ( here ).
* Barebones CM Wiki page by CyanogenMod ( here ).
Comments & suggestions welcome!
If you like my work and want to motivate me to keep working on this (and more stuff for the community) make a donation! any amount is greatly appreciated
=========
CHANGELOG
=========
1.2 (09/06/11)
* Removed the annoying beginner's tips widget
1.1 (06/06/11)
* Added busybox updating
* Added Email.apk and GenieWidget.apk to the core app APK removing section.
* Fixed 90scripts.sh
1.0 (05/25/11)
* Initial release

Great! very usefull
I would also like to find some lightweight replacemments for some apps:
gtalk
- gibberbot (gtalk mod with encryption)
- imo (multiprotocol)
...
Skype
- fring (this can also replace message, phone calling and contacts apps?)
- Sipdroid
- Linphone
- Redphone (has encryption but it is not opensource?)
...
gmail
- K-9 + APG Seems faster and has more features, but I am not sure why it has to be running all the time. I would preffer to open it and check when I want to. Is it me or gmail seems more lightweight in resources?
Maps
- Can we get rid of them working all the time?

devrruti said:
Great! very usefull
I would also like to find some lightweight replacemments for some apps:
gtalk
- gibberbot (gtalk mod with encryption)
- imo (multiprotocol)
...
Skype
- fring (this can also replace message, phone calling and contacts apps?)
- Sipdroid
- Linphone
- Redphone (has encryption but it is not opensource?)
...
gmail
- K-9 + APG Seems faster and has more features, but I am not sure why it has to be running all the time. I would preffer to open it and check when I want to. Is it me or gmail seems more lightweight in resources?
Maps
- Can we get rid of them working all the time?
Click to expand...
Click to collapse
Thanks! glad you like it
Well, for GTalk I've been using eBuddy, and so far it's the best one out there .
I don't use voice calls Skype-style, so I don't know which one to use... Fring seems like a good alternative. I tried to use it as a replacement for eBuddy but I kept going back to it, so its only use (to me) would be a Skype replacement app :/
You may be right about GMail being more lightweight than K-9. I've been testing K-9 for a while now and while I haven't tested it through, it seems waaaaaay faster . I also found this little app which claims to stop the data sync, so it kinda does what you need?
https://market.android.com/details?id=org.r3pek.k9datakiller
Thanks for the feedback =) this little script will keep improving, so stay tuned! ^^.

Hey, great work!
Will try this next week to setup a gb rom (don't know which actually)
I'm quite content with laszlo's froyo the last weeks.
Just out of curiosity (don't want to miss maybe something great new) I'll try ezGingerbread, COS-DS or Yoshi's.

tom0769 said:
Hey, great work!
Will try this next week to setup a gb rom (don't know which actually)
I'm quite content with laszlo's froyo the last weeks.
Just out of curiosity (don't want to miss maybe something great new) I'll try ezGingerbread, COS-DS or Yoshi's.
Click to expand...
Click to collapse
^_^ Thanks! did you try it with the ROMs?
I just updated the script to 1.1 ^^ to comply with GY 1.2 update

greate work , going to try this in the evening when i have some time !

Can you root an XT925 without unlocking the bootloader?

Thinking about buying this phone, but don't wanna void my warranty. I've seen a wealth of information, but I am confused as to what is outdated or not.

timmytucker718 said:
Thinking about buying this phone, but don't wanna void my warranty. I've seen a wealth of information, but I am confused as to what is outdated or not.
Click to expand...
Click to collapse
My HD is rooted while bootloader is still locked

mr_5kool said:
My HD is rooted while bootloader is still locked
Click to expand...
Click to collapse
How did you do it?

timmytucker718 said:
How did you do it?
Click to expand...
Click to collapse
I use the method and files from my XT902 but it works. I don't remember the source of this method (Sorry). I made several changes. My HD is OTA updated from 4.0 to 4.1.2. Here is the method (The risk is yours):
1) Preparation
- SDK & USB Drivers
- Download file from the following address: http://www.mediafire.com/download/13htvihh6c2mhs2/HD.rar or scroll down
- Unzip the file to a specific folder (I put HD folder to the root of C drive)
2) Plug your HD to PC (connect as MTP, unknown source and debugging is on, of course)
3) Do these command (at the directory where you put and perform the adb commands)
- adb push C:\HD\su /data/local/tmp/su
- adb push C:\HD\Superuser.apk /data/local/tmp/Superuser.apk
- adb push C:\HD\busybox /data/local/tmp/busybox
- adb push C:\HD\auto_root.sh /data/local/tmp/auto_root.sh
- adb push C:\HD\unlock_security_module /data/local/tmp/unlock_security_module
- adb push C:\HD\break_setresuid /data/local/tmp/break_setresuid
- adb push C:\HD\mole-plough-ccsecurity.so /data/local/tmp/mole-plough-ccsecurity.so
- adb push C:\HD\mole-plough-lsm.so /data/local/tmp/mole-plough-lsm.so
If any file is pushed unsuccessfully, you have to re-push it, of course
4) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
You’ll see messages about the process. If it fails, then I’m sorry, I don’t know why yet. If it works without “fail”, you success. Here you’ll something like: Unlocked LSM, Do setresuid… I don’t remember them exactly and after all, the command will change from shell ($) to su (#).
5) Load su, Superuser.apk busybox to system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- [email protected]:/system/xbin # mount -o ro,remount /system /system
6) When it’s done, you can remove the cable from PC. Check and see if SuperSU was installed. If it wasn’t, you can download it (SuperSU) from Play Store. Install busybox from Play Store and do the Smart Install. Your HD is now temporary rooted so do not reboot your phone.
7) Install Script Manager – SManager (devwom) from Play Store. Run SManager and choose Browse as root.
- Navigate to /data/local/tmp/ and open auto_root.sh as Script/Excutable (touch and keep for a while).
- Toggle Su on (the icon will change colour to green) and save.
You can reboot and enjoy your permanent root now.

mr_5kool said:
I use the method and files from my XT902 but it works. I don't remember the source of this method (Sorry). I made several changes. My HD is OTA updated from 4.0 to 4.1.2. Here is the method (The risk is yours):
1) Preparation
- SDK & USB Drivers
- Download file from the following address: http://www.mediafire.com/download/13htvihh6c2mhs2/HD.rar or scroll down
- Unzip the file to a specific folder (I put HD folder to the root of C drive)
2) Plug your HD to PC (connect as MTP, unknown source and debugging is on, of course)
3) Do these command (at the directory where you put and perform the adb commands)
- adb push C:\HD\su /data/local/tmp/su
- adb push C:\HD\Superuser.apk /data/local/tmp/Superuser.apk
- adb push C:\HD\busybox /data/local/tmp/busybox
- adb push C:\HD\auto_root.sh /data/local/tmp/auto_root.sh
- adb push C:\HD\unlock_security_module /data/local/tmp/unlock_security_module
- adb push C:\HD\break_setresuid /data/local/tmp/break_setresuid
- adb push C:\HD\mole-plough-ccsecurity.so /data/local/tmp/mole-plough-ccsecurity.so
- adb push C:\HD\mole-plough-lsm.so /data/local/tmp/mole-plough-lsm.so
If any file is pushed unsuccessfully, you have to re-push it, of course
4) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
You’ll see messages about the process. If it fails, then I’m sorry, I don’t know why yet. If it works without “fail”, you success. Here you’ll something like: Unlocked LSM, Do setresuid… I don’t remember them exactly and after all, the command will change from shell ($) to su (#).
5) Load su, Superuser.apk busybox to system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- shell[email protected]:/system/xbin # mount -o ro,remount /system /system
6) When it’s done, you can remove the cable from PC. Check and see if SuperSU was installed. If it wasn’t, you can download it (SuperSU) from Play Store. Install busybox from Play Store and do the Smart Install. Your HD is now temporary rooted so do not reboot your phone.
7) Install Script Manager – SManager (devwom) from Play Store. Run SManager and choose Browse as root.
- Navigate to /data/local/tmp/ and open auto_root.sh as Script/Excutable (touch and keep for a while).
- Toggle Su on (the icon will change colour to green) and save.
You can reboot and enjoy your permanent root now.
Click to expand...
Click to collapse
is this a different method than the saferoot method I have since read about?

timmytucker718 said:
is this a different method than the saferoot method I have since read about?
Click to expand...
Click to collapse
I don't know the saferoot method
I've used this method when my M had failed to root by other method
It's worked on my M and HD

[Root 4.4.X] Pie for Motorola devices

Changelog
1.1 - doh
fixes a bug where exploit only works once.
Pie is a root for motorola devices, should work up to and including 4.4.2.
I had hoped to save this until August however the bug was outed with 4.4.3, and detailed publicly by several people. It now has no value for my purposes. Sucks for me, great for you.
Vulnerability details:
http://blog.cassidiancybersecurity.com/post/2014/06/Android-4.4.3,-or-fixing-an-old-local-root
This is a tethered root (think tethered jailbreak), meaning you have to run it each time you reboot in order to have root access. You do not get system write access, you do get root and busybox.
Usage:
Code:
adb push pie.jar /data/local/atvc
adb push root.sh /data/local/atvc
adb shell chmod 755 /data/local/atvc/root.sh
adb shell /data/local/atvc/root.sh
Expected output:
Code:
Retina:package jcase$ adb push pie.jar /data/local/atvc
5288 KB/s (1538203 bytes in 0.284s)
Retina:package jcase$ adb push root.sh /data/local/atvc
81 KB/s (137 bytes in 0.001s)
Retina:package jcase$ adb shell chmod 755 /data/local/atvc/root.sh
Retina:package jcase$ adb shell /data/local/atvc/root.sh
pie by jcase
want to buy me pie? paypal-> [email protected]
Retina:package jcase$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:kernel:s0
Busybox license -> http://www.busybox.net/license.html
BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
If busybox source is needed please ask me, while it is petty since you can get it from the obvious places, I will gladly package it on floppy disks and mail it media mail at your cost.
FAQ:
Where is source?
On my computer
Will it work on LG G3, Samsung <model>, Nexus 5?
No
Will you root X?
No, don't ask me.
You suck!
Not really a question, but I get this a lot. This is the 5th exploit I have released for MotoX, bite me.
This doesn't work, will you help me?
No, ask the community for support
Will you make this work on X?
No, this exploit, as it is, will only work on motorola phones, and only some.
Will you do this for me?
No
This doesn't work!
Then you are probably running firmware that has been patched, you should have bought a dev edition.
Will you X?
No
What is your favorite pie?
I like apple pie with vanilla ice cream, and Boston cream pie.

Wow, first 4.4.2 root. This is huge! Everyone owes @jcase a big thank you!

Awesome! @jcase is the man but being a tethered root does this mean we can't flash a custom recovery and or ROM? Since the root access will not stick and as it says on op you have to run it every time you boot the phone? Nonetheless great work man

Just what I was hoping for!!! will we be able to use xmodule? Or does it require write permission as well? I want root for that specific reason
Sent from my XT1058 using Tapatalk

jcase said:
...You do not get system write access, you do get root and busybox..
Click to expand...
Click to collapse
So no modifying of build.prop or other things in /system, etc., not even temporarily? Right?

This is great! I don't see a link to make a Pie donation however?
Paypal doesn't take Pie.....

Nice job, man. Even though I don't own a Moto device anymore, I thank you for working on exploits. Tough, and time consuming game, and your work is appreciated.

Thanks Justin)
Sent from my XT1060 using Tapatalk

Getting this:
Code:
adb shell /data/local/atvc/root.sh
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
su fails because it can't find it.

If only I was as talented as jcase... A job well done sir
Sent from my XT1080M "Developer Edition"

abuttino said:
Getting this:
Code:
adb shell /data/local/atvc/root.sh
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
su fails because it can't find it.
Click to expand...
Click to collapse
That output is expected, and none of that indicates a su failure

jcase said:
That output is expected, and none of that indicates a su failure
Click to expand...
Click to collapse
This is where I get the failure.
Code:
[email protected]:/ $ su
su
/system/bin/sh: su: not found

abuttino said:
This is where I get the failure.
Code:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
Click to expand...
Click to collapse
What device, and firmware build?

So, will this work on the att? or is it for the others who already had root before 4.4.2?

jcase said:
What device, and firmware build?
Click to expand...
Click to collapse
{
"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"
}
Moto X

abuttino said:
Moto X
Click to expand...
Click to collapse
add me to gtalk/hang outs so we can debug it

jcase said:
What device, and firmware build?
Click to expand...
Click to collapse
Hi Jcase, for me works the first time, after reboot and try to re root, show the same issue
Code:
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell chmod 755 /data/loc
al/atvc/root.sh
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell /data/local/atvc/ro
ot.sh
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
thanks

tomorow i can test it too
thanks @jcase for ur work
u are the man

Yeah i see the issue, i didnt clean up my mess, fixing
megapinky said:
Hi Jcase, for me works the first time, after reboot and try to re root, show the same issue
Code:
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell chmod 755 /data/loc
al/atvc/root.sh
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell /data/local/atvc/ro
ot.sh
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
thanks
Click to expand...
Click to collapse

Fixed, download package1.1.zip and try that
megapinky said:
Hi Jcase, for me works the first time, after reboot and try to re root, show the same issue
Code:
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell chmod 755 /data/loc
al/atvc/root.sh
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell /data/local/atvc/ro
ot.sh
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Program Files (x86)\stillthisguy\Moto X Toolkit>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
thanks
Click to expand...
Click to collapse
abuttino said:
This is where I get the failure.
Code:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
Click to expand...
Click to collapse

busybox ls --color and many other commands "Working"

have you got bored of your one Text colored terminal ?
when you look at the results you always are confused ?
well .. you came into the right thread
I'm here today to show you how to make every busybox command fully functional
I was trying to make this command work but no success
Code:
#ls --color=always
then i ended up making busybox fully functional
Note: you must have rooted device and custom recovery and SDK tools " incase you don't have adb.rar "and your phone developer mode and USB debugging checked .
go to your SDK tools press sheft and right mouse click and open cmd here
________________________________________________________________________
now .. lets get to it shall we ?
1 - reboot into recovery and connect your device in your PC
2 - type in these commands in your PC command prompt you opened in order :
Code:
# adb shell
# mount system
# cp /system/bin/sh /sdcard/Download/sh
#adb reboot
3 - reboot your device
4 - download this busybox app and start it
jrummy.busybox.installer
5 - you'll see in the app's INSTALLER icon a location /system/xbin
change it to /system/bin
6 - open app's settings "upper right corner beside the three dot's" and check all what's in the installer settings
7 - press back and click install " your phone will boot into recovery and install the busybox "
8 - after finishing the process your device will reboot normally but wait a minute !!! SU is not working anymore :crying:
9 - reboot your device again into recovery !! " I'll try to fix it for you "
10 - type in these commands in order :
Code:
#adb shell
#mount system
#cp /sdcard/Download/sh /system/bin/sh
#chmod 755 /system/bin/sh
#adb reboot
and we are done
look at the attachment below this is how your terminal will look like and error free

I'm sorry about this post
apparently I was kinda mistaken
I think what happens that lead to this is
when you write down the applet's name in terminal the device start to search inside bin file first .. if the applet was not found in bin .
the device will start to search on xbin file and maybe the whole storage for that command
so .. since there are some applets in bin are the same one in busybox and I was able to locate them "took me like an hour to do so"
and these applets are :
Code:
[COLOR="blue"]blkid
brctl
cat
chmod
chown
clear
cmp
cp
date
dd
df
dmesg
du
grep
gzip
hd
id
ifconfig
insmod
ionice
ip
kill
ln
ls
lsmod
lsof
mkdir
mke2fs
mknod
mkswap
mount
mv
netstat
nohup
ping
ping6
printenv
ps
readlink
reboot
renice
rm
rmdir
rmmod
route
sh
sleep
swapoff
swapon
sync
top
touch
tune2fs
umount
uptime[/COLOR]
there are a lot of difference in results between the factory applets and the busybox applets
if you want to see the difference install busybox in /system/xbin and in terminal type one of these applets above like this :
for busybox applets result :
Code:
busybox [I][COLOR="blue"]applet[/COLOR][/I]
for system applets result :
Code:
[I][COLOR="Blue"]applet[/COLOR][/I]
it might not be a new thing but for me it is
I just wanted to share that info for the ones who doesn't know
Edit : there is also one applet in system/xbin which is " nc "
thanks .