Related
For all you guys constantly flashing kernels,
I have made a little app to make sure that all command are typed in correctly & to make it a little easier.
You can find it here.
http://minooch.com
Let me know if you think I can make any improvements.
I've only tested it with my N1, but there is no reason why it wouldn't work on other android phones - its just using adb & fastboot. Having said that, it will obviously need the AndroidSDK installed (well partly) & the only other requirement is .NET 2.0 or up.
I finally got around to posting the new version - Version 1.0.1 - The main feature that has been added is synchronise. For example, you can select a folder full of music on your PC & it will copy all the music to your phone (if it's not already on there), & if there is music on your phone thats not on your pc that will copy over as well.
26/05/10 - Small change - Version 1.0.2 - ADB location is now saved in registry
17/08/10 - Version 1.0.3 - Added flash radio (via fastboot) - It will reboot into the bootloader, flash the radio & then reboot the phone
30/08/10 - Version 1.0.4 - Added a donate link
25/11/10 - Version 1.1 - It now has the option to verify the MD5 before flashing a radio
08/01/11 - Version 1.2 - Language can now be changed - Language.lang has the values of all labels, buttons & comboboxes
Known Bugs: (wth synchronise)
If a folder has a space in its name, it's contents won't sync properly (currently working on a solution)
If you delete a file/folder on your phone/pc (not both) it will be copied back next time you sync (not sure how to fix)
The destination folder must exist already (/sdcard/music or where ever you choose), but obviously not the folders what will synced they will be created
Cheers,
Minooch
Feel free to donate
Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)
rcxquake said:
Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)
Click to expand...
Click to collapse
didn't know that command will add it now. - edit: Done
Cheers,
Minooch
I'm happy with ADB so not going to be using this (don't mean that the way it sounds!) but just thought if the user is pushing the .ko over adb, will they need and "adb remount" option as well?
yep you will need to remount - but that is automatic.
Using my tool, it takes less steps & is faster
great tool! thumbs up!
Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.
mikroN1 said:
Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.
Click to expand...
Click to collapse
Thanks,
Will have a look into it.
looks like a nice tool.. gonna give it a try
good work man
Hey man I'd have to say that I'm getting used to the command line that I nearly forgot there's something in the world called GUI It's really a great tool for lazy guys like me (even I've written a simple shell script). Good job!
Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.
MikroN1,
I will add that later today when I get home from work.
Cheers.
Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.
mikroN1 said:
Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.
Click to expand...
Click to collapse
mikroN1,
It nows saves the ADB location to registry
devil126 said:
Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.
Click to expand...
Click to collapse
I'm a little confussed by what you want. Are you wanting a manual for ADB GUI or how to use ADB?
This is very good. Downloading now.
New Version - 1.0.3
Added flashing radio via fastboot
It will reboot into the bootloader, flash the radio & then reboot the phone
using ADB sync for sqlite DB
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.
BTT
asinghma said:
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Bringing this thread to top.
Can anyone provide the source for ADB sync (prob from ADB_GUI tool)
Thanks,
Think you should add a donate button somewhere in your app too!
Vulpix said:
Think you should add a donate button somewhere in your app too!
Click to expand...
Click to collapse
Done Feel free to be the first to donate
Oh, If you would like me to add any features, let me know
This is a BETA version and will have issues
About
I got tired of using ADB by hand for a lot of operations, and thought well hey let's write something for that. I know about DDMS and ADB Explorer, but they aren't always exactly what I want/need.
BETA
Yeah this is a beta version and will have issues.. No warranty, use at your own risk, etc. I'll try to update this in the future. I have a lot of ideas of things to add/improve/fix still.
Requirements and Recommendations
- Required: .Net 3.5 framework
- Required: A working "adb shell" setup
- Recommended: writable /sdcard
- Recommended: root (via su) - note that a lot of things should work without root, but I haven't done any extensive testing on that
- Recommended: busybox
Features
- (also root) Explorer
--- View / Edit files directly in Notepad (optionally converting dos<->unix newlines)
--- Retrieve / add / replace files
--- Rename / delete/ chmod/ chown / checksum
--- New directory / symlink
- Locate (find all filenames matching a certain string)
- ADB shell
- ADB logcat
- ADB (command log)
- Packages
--- Install package (system copy, user copy, ADB install, with or without ODEX, etc)
--- List / backup / remove user and system packages
Retrieving / viewing / editing / replacing / adding files all use workarounds to be able to do this to files that cannot be directly pushed/pulled by ADB, but this functionality does depend on busybox being available.
Donate!
Donations appreciated, you can do so here: http://www.jongma.org/dx.php
Install
Extract the ZIP and put the EXE in the same folder where you have ADB. Also make sure your phone is working with the normal "adb shell" command.
Usage notes
- Please make sure your device is connected in USB debug mode before using ADB Magic !
- Please make sure you do not have the SD cards mounted to your PC !
- This has been developed only with a Galaxy S, so I'm not sure how well it'll work with other devices
Download
<< 1.0, 625
Awesomesause, i would recommend reposting in the android dev forum
edit: should have read ur post xD...
New version and moved ...
I have to say i tryed it on my x10,, and great works good, this program has lots of promise, Thank you and top marks for the work so far keep it up...
Works fine on my X10i. Great work. Very promising.
crap no linux version
nice utility,It works well for the Evo
very nice....works on droid
Thanks for this really useful program. It works great on my X10i.
very nice! works with xdandroid on tp1.
Absolutly great, thank you very very much for this! Extremly helpful!
This is pure awesome, thank you!
Updated to 0.9, now works with ROMs with the latest busybox
Found an issue
Hey, ive found you cant ctrl+c in shell, when i was testing my bootanimation;
#bootanimation
you usually hit crtl+c to stop, in this case I could not, so I had to restart the phone.
Otherwise, looking really good so far hey! Keep up the good work!
Super cool. Mad Props.
HI Chainfire!
I love this app, it's great! I've stumbled across a problem though... I upgraded from JPC to JPK on the weekend and since then it hasn't been working, even after going back to JG4. All the times I've tried it, I've been rooted. It comes up with an error box that just says ! in it.
I haven't changed any of the adb files, and I can also use adb shell manually. Any ideas?
Haven't flashed to JPK yet so no idea, but I'll see once I do
No worries!.
I moved it then ran ADBMagic so it could look for ADB, then put ADB back and selected it, still no luck. Also, I flashed back to JG4 then rooted and it still wouldn't work.
I also noticed that for some reason, it can't start the ADB server and issue the toolbox ls -l / command, even with busybox installed but it CAN see the live logging.
I'm stumped :S
-edit-
I got ADB File Explorer and tested it again. It works, but can't read all directories as it's not able to get su priveliges. I seem to remember the first time I used ADBMagic that SuperUser on the phone asked to allow ADBMagic... am I right or remembering badly? If so, it's not asking me to allow it anymore, across the different roms/roots. Strange.
OK, don't worry about my problem at the moment mate, it seems it's the symptom of a larger problem not associated with your program
Nitephyre said:
OK, don't worry about my problem at the moment mate, it seems it's the symptom of a larger problem not associated with your program
Click to expand...
Click to collapse
Care to elaborate on what this is? I'm having the same problem on my Rooted Captivate JH7, and I need it for the Jupiter GPSfix.
I think all of you PS3 owners here already know about the Jailbreak tool that allows you too execute unsigned code on the PS3. That opens the console for a lot of homebrew possibilities(mplayer port maybe?). The source code for the exploit leaked and a dev called KaKaRoTo managed to get it to be executed from a N900. Yesterday KaKaRoTo released his souce code and today someone already ported it to the Palm Pre. This quick port was possible because the N900 and Palm Pre both share the same USB controller(mUSB) which happens to be the controller used by the Droid/Milestone.
Here is some info from KaKaRoTo's blog:
Q: How hard is it to port it to a new device ?
A: Well, I’ve just separated my code from the N900 specific stuff, so it’s quite easy, there are mainly two functions to write, one to get and one to set the USB address.. two other functions that only return some static result depending on the configuration of the controller (the name of the endpoints, and whether the controller supports high speed or full speed mode).
Read the README file provided with PSFreedom, and check the psfreedom_machine.c file for specifics on what to implement.
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
That should be enough!
Ok this is it for now with the FAQ. Next time, I’ll tell you all about my experience, what problems I encountered and how I fixed them, maybe it will help others!
Click to expand...
Click to collapse
http://kakaroto.homelinux.net/
Some people over the HTC Desire boards are already working on a port but Desire's controller is a different one(MSM72K) so they might take some time and it will be of no use for us
http://forum.xda-developers.com/showthread.php?t=772795
So, any dev here willing to give it a try?
according to zzg in the desire forum, this is what you need to do. no source changes.
Well you don't really need any changes to get it compiled against Droid's kernel, a quick and dirty way by looking at psfreedom's make file:
make -C /path/to/droid/kernel/source M=/path/to/psfreedom/source ARCH=arm CROSS_COMPILE=/path/to/android_ndk/tree/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi- EXTRA_CFLAGS=-DENABLE_MUSB_CONTROLLER modules
Click to expand...
Click to collapse
You can get the source from motorola.
Has anyone been successful with the exploit?
On the wiki it shows that it's in progress, but no info on who is working on it
hxxp://psfreedom.com/wiki/index.php?title=Device_compatibility_list
The guys over in the Milestone thread are beginning to get somewhere it seems, and someone in the desire thread said they've almost got the Milestone version working.
Not sure it means anything to the droid-ers though
Ahhhh I want a Droid version! I wish I could code!
Patiently waiting for the Motorola Droid Port....
Anybody know who is working on milestone/droid port?
desolateone1 said:
according to zzg in the desire forum, this is what you need to do. no source changes.
You can get the source from motorola.
Click to expand...
Click to collapse
Tried that. It didn't work, though I'm not familiar with configuring kernels. I have a compsci degree, but I just haven't ever played with them. Didn't figure it'd be as simple as this but thought I'd give it a go for the community... anyone want to give me a new clue?
Edit: I configured the kernel with 'make defconfig'
Where did you get the motorola source kernel?
https://opensource.motorola.com/sf/projects/droid
http://tinyurl.com/droid-ks-ese81
http://android.git.kernel.org/?p=ke...1;hb=34485287cb92a298eb6110926b729bf40bf3ba69
The third link is to the kernel space tree and I took the "snapshot" from there.
Got the NDK from here...
http://developer.android.com/sdk/ndk/index.html
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
freehood4all said:
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
Click to expand...
Click to collapse
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
zerosignal0 said:
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
Click to expand...
Click to collapse
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
freehood4all said:
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
Click to expand...
Click to collapse
Awesome! Thanks for the info, I was just wondering where the dev work was coming from. Also thanks a bunch for the boot_image heads up because I was just about to flash it over but wouldnt have been able to test it for a few hours.
-Z
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
zerosignal0 said:
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
Click to expand...
Click to collapse
Place any .pkg files on the root of a thumb drive thats formated to FAT32
As for backups you can put backups under /dev_hdd0/game/LAUN12345/GAMEZ "This is the path if you are using the original backupmanager.pkg and not some stealth backupmanger"
For games on an external I believe you put a folder named "GAMEZ" on the root of HDD. I haven't tried with external yet, so correct me if I'm wrong.
I will let you know when I get out of work. I have setup and saved my rom with the kernel changes so I can quick change when necessary. Thanks for the update on the file paths as well.
-Z
I'm totally lost right now can someone walk me through on how to do this? I have cm6 on my droid
You essentially are kinda following the same steps for flashing the boot image for getting manual root and some older roms. The instructions are pretty straightforward but make sure that you take a nandroid backup before making any changes.
I am running chevys SS 4.7 rom but I believe the kernel versions should be the same. As soon as I get out of here Ill update with the results.
-Z
Epic 4G All in One Root and Recovery 2.04 for Windows, Intel Mac, and Linux
***SORRY, AIO v2.04 IS CURRENTLY BROKEN FOR EB13, FIX IS COMING ASAP, USE ONE CLICK ROOT FOR NOW***
***WARNING NOT TO BE USED WITH ANY SUPPOSED LAGFIX, IT WILL SCREW UP YOUR SYSTEM AND YOU WILL NEED ODIN TO RESTORE***
OK, what started as scripts for my Mac turned out to be a big scripting project for Windows, Mac, and Linux.
This gives root and clockworkmod for all of the major operating systems.
This is like an Epic 4G swiss army knife, providing all of the basic tools in one convenient download.
These scripts give you a menu that allows you to choose between the following:
1) Simple One Click Root and ClockworkMod 2.04 - based on one click root 2.5.4 by noobnl and firon, compatible with Eclair and Froyo, ClockworkMod redirector for Froyo included
2) Andromeda Kernel 1.4.1 by noobnl - custom kernel with root, busybox and superuser, for 2.1 Eclair
3) SDX Stock App Remover 1.5 apk - back up and remove Stock Apps for rooted users
4) Wireless Tether 2.0.5-pre13 - Open source wireless tether for rooted users
5) Simple Root Uninstaller 2.04 - removes one clicks / z4root, Eclair and Froyo compatible
6) Reinstate Stock DI18 kernel for 2.1 Eclair
7) Reinstate Stock Samsung Recovery for Eclair or Froyo, uninstalls ClockworkMod and redirector
You could call this a noobnl festival for all operating systems...
PLEASE READ ALL MY NOTES BEFORE INSTALLING, I'VE FOUND LOTS OF PEOPLE HAVEN'T READ OR FOLLOW THE INSTRUCTIONS... FOR WINDOWS USERS, DRIVERS NEED TO BE INSTALLED CORRECTLY FOR THIS TO WORK.
http://dl.dropbox.com/u/500010/epic.aio.v2.04.zip
New! Now compatible with Android 2.2 Froyo, with ClockworkMod redirector included in script. Won't allow Eclair kernels or recovery to be installed on Froyo. ClockworkMod install now in Simple Root script. Wireless Tether added. Stock Samsung Recovery for Eclair and Froyo added.
NOTES: - Sorry so many in this page, but they really need to be listed Please at least read through until the end of the instructions before running this.
This is an all-in-one installer for the Epic 4G. When running this, the menu presented allows you to choose what you want to do, and does not install everything in one run. It is intended to only perform one menu item at a time.
If you just want to remove bloatware and run rooted apps, and don't intend to flash ROMs or rooted kernels, then just the Simple One Click Root will suffice by itself. This script now has a menu option to install SDX Stock App Remover, which is great at backing up and removing the Sprint bloatware. That will make it easy to bring back to stock and just remove root if it's necessary. Know what you're removing with the Stock App Remover, as removing the wrong system apps will get you into trouble!
Installing the Andromeda Kernel from this script does not require ClockworkMod Recovery. It can be uninstalled by flashing the stock kernel. The Andromeda kernel is already rooted, and does not require the one click root.
Clockwork Mod Recovery is used to flash other kernels, ROMs, and Mods. Instructions for booting into ClockworkMod are listed below. This is now installed with the Simple One Click Root, and a backup should be performed right away after installing it from the menu in ClockworkMod.
The past couple of generations of one click roots are safe with rooted kernels and ROMs, and are installed in /system/xbin, which is the last location in the path. Rooted kernels will just take precedence when installed.
Both the Simple One Click Root and the Root Uninstaller will remove the older joeykrim roots that use the hacked playlogo.
Because Superuser.apk is installed, superuser will ask permission before any program is granted root access. This is to ensure that no rogue program takes root privilege without your knowledge.
Booting into Clockwork Mod: Power down phone. Press and hold the camera button, then the volume down button, and then the power button, continuing pressure on all 3 keys until the Clockwork Mod menu appears, which will be seconds after the Samsung logo appears on the screen. The menu for Clockwork Mod Recovery has green text, instead of the blue text used by the stock Samsung recovery. Navigate up and down using the volume up and down keys, the power button goes back, and the camera button acts as enter key.
INSTRUCTIONS:
Before running, do the following on the phone from the home screen :
Press Menu > Settings > Applications > Development, and make sure USB Debugging is checked on your phone.
WINDOWS:
Samsung drivers are required:
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
Note: Driver installation under Windows 7 has been a pain for some, and has been the number one reason why people haven't been able to run the script successfully.
Also: DO NOT RUN run.bat as Administrator (by right clicking on the file and running as admin), the script will fail! Thanks to shepscrook for pointing this out.
Extract the zip file, and go inside the folder that was created with the same name.
Open run.bat (or just run) type in a number option, and press enter. Really easy (Hopefully ).
INTEL MAC & LINUX:
Note: Mac and Linux users may be prompted to enter administrative password, as adb server requires sudo permissions to start.
No drivers required.
Extract the zip file.
Open Terminal. Use the cd command to get to the directory. If you extracted inside the Downloads folder, it would be easy in Terminal as so:
Code:
cd ~/Downloads/epic.aio.v2.04
Now give permissions and run it:
Code:
chmod +x run.sh
./run.sh
THANKS TO FIRON FOR CODE MAKING THE SAME SCRIPT BOTH INTEL MAC AND LINUX COMPATIBLE.
After choosing the menu selection, just follow the instructions. I did try to make this very easy for you
THANKS TO NOOBNL FOR PERMISSION TO USE HIS STUFF, AND FIRON FOR HELP WITH SCRIPTING.
Other Credits:
joeykrim - original exploit
skeeterslint - busybox
koush - Clockwork Mod
These are just modifications of work already done by the aforementioned. I just had the vision to unify all of it into one master tool that can be used across all computers.
LINKS TO ORIGINAL RELEASES:
Handy if you're having trouble with this release, or just want to learn more about the originals:
One Click Root 2.5.4 by noobnl
ClockworkMod Recovery 2.5.1.0 by noobnl
Andromeda Kernel 1.4.1 by noobnl and Kernel Sources
SDX Stock App Remover 1.5 apk
VERSION HISTORY:
1.01 Added chmod to adb.lin and adb.osx to ensure that scripts work right first time, especially in linux.
1.10 Major rewrite for Mac and Linux unifying into one master script, with very generous script contribution by Firon. Scripts are now more organized and efficient. Remount now in /system/xbin. Uninstaller has rclean file that lists all files to be removed from phone, and now runs from phone to reduce visible rm failed errors. adb server now restarts after exploit, which greatly reduces chances of phone losing connection. Command line input options. Has busybox by skeeterslint. Added menu option to reboot phone.
1.11 Changed adb alias to include sudo, to prevent permission errors. Will prompt for password on first run if necessary.
1.12 Checks to make sure phone connection is seen before and after exploit, and after reboot. Thanks to Firon for the timer code. Checks to make sure Clockwork mod install reboot takes place, therefore knowing if it was properly installed. Added both methods for installing clockwork mod, and menu option to install SDX Stock App Remover 1.5 apk.
1.13 Smarter script, detecting if kernel is rooted, should eliminate problems with Clockwork Mod installs. Added Andromeda Kernel 1.4.0.
2.00 Rewritten based on One Click Root 2.4.0 by noobnl and Firon. Made compatible with 2.2 Froyo. Stock Samsung Recovery added. Added Wifi Tether. Will detect if Froyo is installed on phone and abort if trying to flash Eclair kernels or recovery.
2.01 ClockworkMod redirector by noobnl included, only installs if Froyo is detected.
2.02 Incorporated improvements from One Click Root & ClockworkMod 2.5.0 by noobnl and Firon. Includes Firon edits to ClockworkMod redirector files. Reinstating Stock Samsumg recovery will install appropriate bin for Eclair or Froyo automatically.
2.03 Fixes a couple of script errors, minor edits.
2.04 Updated to latest adb binaries, which affected linux users. Wifi tether updated to pre15. Playlogo replace fixed in batch script. Clockworkmod redirector files fixed to fit inside dk28 /system folder. More script fixes.
Bonus: Command line tools built into script:
e --runs the exploit, to get su from adb shell, if kernel isn't rooted
k --shuts down adb with adb kill-server
r --reboots the phone by starting adb server then calling adb reboot
s --restarts adb server, by first killing it, then starting it again
This can be evoked from the command line as so, saving some typing:
Windows:
Code:
run e
run k
run r
run s
Mac / Linux:
Code:
./run.sh e
./run.sh k
./run.sh r
./run.sh s
Enjoy!
Sorry no link here, it's in the sdx epic 4g developers forum, the file is about 13mb hosted on my dropbox account. I couldn't find a way to split it into just 2 files, all my archive programs only handle diskette and cd sizes.
I've been working on this for a while now, and figured I'd share it on xda now, especially since the post by mkasick here on the simpler root method inspired me to name the root and removal methods "simple".
I'm new at xda, I'm just a scripter, but any developer can take a look at the script and see it's legit.
If a moderator could unlock me to put the link directly in the post, I'd be much obliged... I do realize the need to prevent spammers.
OK, signing off, hope you all enjoy it!
DRockstar
OK, this has been updated for those interested. I know some of you have checked this out at the SDX forums. I'm still waiting for permissions to post outside links so that you can download it directly from here. Sorry for the inconvenience.
Used your root and worked flawlessly. Awesome job!!
phantomevo77 said:
Used your root and worked flawlessly. Awesome job!!
Click to expand...
Click to collapse
Thanks for letting me know that it's been useful! I spent a lot of time perfecting it.
Download link is finally up...
Thanks to the moderator for letting me know what I needed to do.
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Sent from my SPH-D700 using XDA App
My last post sounded mean...I meant it as people just don't appreciate some of the hard work on here
Sent from my SPH-D700 using XDA App
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
LordLugard said:
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
Click to expand...
Click to collapse
Yes, you'll be fine if you want to test out the Andromeda kernel in this release. The Root Uninstaller will remove it without problems. That is one reason I included it in this release, so you can at least try one good rooted kernel safely.
For Mac and Linux users, it is imperative to create a backup in clockwork mod before testing out any other kernels and ROMs. Windows has Odin3 for flashing a full stock system to the phone as a backup, while no alternative exists for Mac or Linux. There is a stock ROM posted by noobnl in the Epic 4G wiki, which I think is the best alternative we have right now.
Sent from my SPH-D700 using Tapatalk
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Dulanic said:
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Click to expand...
Click to collapse
This expects you to perform only one action at a time, and it should automatically reboot the phone.
The exception is installing the SDX Stock App Remover, which simply installs the apk to the phone. That can be removed easily like any other app.
Sent from my SPH-D700 using Tapatalk
Oh I see, I didnt quite read it right
A_Flying_Fox said:
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Click to expand...
Click to collapse
Yeah, I was just new to this particular forum and didn't realize what I needed to do... it is now in the wiki, so others can see it... I expect this to be very popular once people realize just what it is and how useful it can be.
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
spitefulrain said:
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
Click to expand...
Click to collapse
Well, firon and I worked together on script making the bash script Mac and linux compatible, and other things. Firon has been a valuable help in contributing code, he's gifted with scripting. He uploaded his changes to a 2.3.0 version in the SDX forums, but I guess that was never reflected in the official posts, or he just uploaded the changes without changing the version...
You can see here:
http://forum.sdx-developers.com/epi...ck-root-for-the-epic-4g!/msg102968/#msg102968
Edit: if you click the download link for the 2.2.9 one click root, you'll actually download 2.3.0 the original posts needs to be updated to reflect the update.
Sent from my SPH-D700 using Tapatalk
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
leebo73 said:
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
Click to expand...
Click to collapse
What OS version are you using? If Windows, have you loaded the drivers? If you're getting a message that the phone is offline, then your phone connection is not being recognized.
You do have debugging checked in the phone's application preferences?
If you're running Windows 7, drivers are a notorious pain, and they need to be installed correctly for any scripts like this to work.
Rockstar, this is a very underrated app, swiss army tool for the Epics for sure. Worked flawlessly on my sister's phone installing root, CWM, and SDK app remover. Appreciate your work ... if I get time, I might develop a simple frontend for this. You, Firon, noobnl, and mkaslick are awesome
Very nice package, downloading now. This should make it much easier to restore things back to how I like them after all the re-flashing to stock I do.
PreambleI oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
thebic said:
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?
What version of twrp are you running?
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Yeah you could use adb sideload in twrp.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P
Re-read my cited post: I've edited it.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers
thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.
Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?
You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P
OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATIONVery likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!
Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Yep! Well good luck
jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post