[Root] SimpleRoot 1.5 (Revised - Linux/Windows) - myTouch 3G Slide Android Development

http://www.nickbetcher.com/~nbetcher/SimpleRoot-v1.5-Linux.tar.gzHere you can find the revised version of SimpleRoot. It has somewhat major changes that blend in the combination of Wes and Eugene's findings together and separate from one another. As Wes has silently left the community for the Vibrant (as I understand it - please clarify if you want Wes) I have been unable to contact him.
Consequently I am posting revised version of SimpleRoot for the people whom are new to the community or people who want a more streamlined process that uses Eugene's Clockwork update.zip and Wes' SimpleRoot package. Using Eugene's update.zip fixes problems with gaining root access once you have flashed your ROM (SuperUser APK was apparently missing in Wes').
It's been generally accepted that SimpleRoot is fairly unnecessary once you flash the ENG nbh. There was controversy over the ENG nbh, but Eugene has disproven those opinions. For those of you who still want to use SimpleRoot, here it is.
Download: For Linux v1.5 (4shared).
Download: For Windows v1.5 (4shared).
Changes (for v1.5), they are as follows:
Switched from Wes' update.zip to Eugene's update.zip to eliminate problems gaining root access (SuperUser APK was apparently missing in Wes') after the ROM was flashed.
Changes (for v1.4.1 - WINDOWS ONLY), they are as follows:
Apparently the usb_driver package I had from the Android SDK didn't have the HTC Espresso's hardware IDs present. Added those so it will allow you to use the packaged drivers for device installation.
Added @ECHO off into rootme2.bat.
These changes do not affect the Linux package since the Linux scripts work and Linux doesn't need a special driver.
Changes (for v1.4), they are as follows:
Changed a lot of the text formatting for the Windows scripts, including fixing line feeds, quotation marks, command echoing, and grammatical changes.
Added the most recent copy of the Android SDK's Windows USB driver since users who have never installed the driver need an easier way to get it. (Especially if they are on limited broadband)
Added the USB driver as a requirement in the Windows script since it is a fairly important requirement.
{
"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"
}
Added a .sh extention to the Linux script filenames.
Added a ./ in front of "adb" in the loop.sh script so it uses the adb in the local directory of the SimpleRoot extracted archive versus erroring out in a loop (in the likely event the user doesn't have adb installed system-wide). This preserves the consistency already in the other scripts.
Packaged the Linux files into a subdirectory in the tar.gz file versus extracting the files into the current directory (which is highly irritating
).
Bumped version number to 1.4.
Added myself into the credits.
Modified the Windows Readme file to reflect the directions provided from the script.

Thanks nbetcher!
As I understand it Wes is working for both devices now, not sure though.

Quick question this worked perfect the first time but when i tried to put a rom on my sd card from clockwork it wouldnt see it when i clicked install from sd so i rebooted and i saw superuser on stock and i couldnt get back into clockwork since then and now i cant re root again it keeps saying device not found any ideas

Related

[Q] I built a custom kernel for my phone, but how do I test it?

I'm trying to make a custom kernel for the Samsung Gravity SMART using sources from the unofficial CM9 port for the Gio/Ace (which both use very similar hardware to the Gravity Smart). What I've succeeded at so far:
1) Acquiring the source, both for the CM9 kernel and for the stock Froyo kernel
2) Searching for the device-dependent references in the stock kernel
3) Porting those changes over to the CM9 kernel
4) Getting everything to actually compile
5) Acquiring the stock CM7.2 source
6) Creating device makefiles (i.e. BoardConfig.mk, etc)
7) Building CM7.2 using kernel built in step #4
8) Putting the various img files into an Odin-compatible .tar.md5
9) Actually flashing to the phone.
And for all that work, I got.. a soft-bricked phone (fortunately, I have an Odin file for stock firmware). The phone boots to a SAMSUNG logo (not flashing/throbbing).
So my question is: how the heck do I figure out what's actually failing? Is there a bootloader to unlock, and if so how do I unlock it?
I strongly suspect I'm dealing with a bootloader problem. If I unpack the stock boot.img, edit init.rc with a commented line, repack the boot.img and try flashing it, I get the same behavior (stuck at SAMSUNG).
Any tips for unlocking the bootloader?
The good news is that it doesn't seem to be a locked bootloader--at least, I figured out how to flash a customized boot.img that contains a stock kernel and a modified ramdisk.
The bad news is that my kernel STILL doesn't boot, and I still have no idea how to approach troubleshooting/debugging it. Any tips?
Connect your phone to USB, go in the SDK folder and start ddms.bat. Let it load the GUI, then start your phone. At this point it should come up in the dalvik debug monitor.
Select your device on the left side and see in real time what errors it pops-up
DeuXGod said:
Connect your phone to USB, go in the SDK folder and start ddms.bat. Let it load the GUI, then start your phone. At this point it should come up in the dalvik debug monitor.
Select your device on the left side and see in real time what errors it pops-up
Click to expand...
Click to collapse
thats a nice piece of info, can you elaborate some more?
{
"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"
}
That's pretty much it. You can also request screenshots, explore files inside on the phone, request logcats and explore process logs.
It's a nifty tool
Thanks for suggesting DDMS, unfortunately it doesn't provide any useful information. It looks like it's just not booting the kernel at all.
I think the problem has to do with the bootloader--researching other, similar phones, the boot loader firmware is tightly coupled with the kernel, particularly the modules that actually interact with the flash filesystem. Since those modules are Samsung-proprietary, my only choice is to either back-port as many features from newer kernels into the stock kernel source, or figure out how to hack the boot loaders to work with a newer revision kernel. It would be a lot simpler if Samsung released a GB update, but fat chance of that ever happening.

[REQUEST] Make apk with script

I am a not developer and dont know how to create apk, so i have a request to any developer.
Can make apk with script file, i have ready script file to push in apk
simple apk with one button to run script and progress bar.
SU permission required too.
for future updating of the script that could be replaced only into a script file in the apk
If you can make that simple apk tell me, then i publish the script. Thanx
Can't you just use script manager?
Sent from my LT15a using XDA
yes i can but first must install script with update.zip
next run script with terminal or script manager or adb shell from PC
Apk is universal and simply way to use, and dont require install update.zip before (i think so)
so meybe any dev help me?
What exactly are you looking for? A apk that runs scripts you give to it or just a apk that runs the script your talking about?
If it's just an apk that runs several scripts, the method to get them onto your phone will be the same I.e. You will still need the update.zip or adb push.
If it's just for one script it only takes a few lines of code, take a look on the portal one of the devs published a video on how to create a root app.
Sent from my LT18i using XDA
ok so i add script to attachment
Script make nandroid backup CMW
example of another application:
this is content of example apk
{
"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 need to put script file in apk archive, example (or another folder in apk)
for future simple edit script without recompiling apk.
but i dont know how to compile this apk.
I'm still struggling with what exactly it is your looking for, if you code an apk yourself theirs more chances of bugs rather then say using a terminal emulator from a developer with a lot of experience. As for the progress bar, you would have to modify the script itself to report the current progress. Unless you want to get into dev then I would suggest you stick with terminal.
Else check this video from Adam, it gives you the basics and he also includes a link to his open source "shell" class.
http://www.xda-developers.com/android/how-to-build-an-android-app-part-2-writing-a-root-app-xda-tv/
The basics would be to get that app up and running yourself, make sure that it runs commands you give it. Then just have your script somewhere like "/sdcard/script.txt" and pass the parameters something like "su -c", "sh /sdcard/script.txt". That way you could always update /sdcard/script.txt and then just run your application.
It's easy to run scripts from in an app. But you need to code it not edit an excisting app
Are you wanting an app to automate cwm backups? ( my cwm autoinstaller does this )
I don't understand what you are after either lol.
Pvy
Sent from my TEAM Powered Arc S

[SOLVED] I can't install Cygwin (No Packages Found) Windows 7 64bit

Hello,
::Look At the End of the Post to Find the Solution::
I'm having a big problem here installing Cygwin on Windows 7 64bit. When I try to run the Setup.exe and I choose install from local directory and I go to the page where I click on the arrows to install the packages I just notice that it says up there that there is No Packages Found...!
here is an Image showing what I mean:
{
"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'm trying to install ( Dsixda Kitchen ) so I'm using links from his Thread: [KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
I installed JDK for both 32 and 64 bit, and of course I have android SDK installed, I also went to change the PATH in the: Environment Variables and added the Path to my JDK excutables which is like that: [ (Other Programs here)......;H:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files (x86)\Java\jre7\bin;C:\Program Files (x86)\Java\jdk1.6.0_20\bin ]
as you can see I have all paths to all Java Installed on my PC.. and I have a friend running Dsixda Kitchen on the JRE 7 alone installed instead of the JDK from Dsixda's Thread and he says it's fine either ways, also many people confirmed the same.
I tried re-downloading Dsixda Kitchen packages and also his Cygwin packages and when I tried to install I got the same thing in the picture above that there is: No Packages Found
I installed the Java JRE and JDK before trying to install Cygwin as explained in Dsixda Kitchen's thread for installing for windows post #3
I'm just trying to have Dsixda Kitchen running, and so far and after many days of trying I have no luck...
I even tried with a virtual machine running windows xp sp3 32bit and still the same error that there is no packages found!!
I hope I could find here some help as I tried visiting cygwin site and I can't find help there in their mailing list!! it's a real pain to browse there!
thanks guys
::EDIT - Solution::
the problem was that when u run the setup.exe u just go on with the defaults... u just click on Install from locale directory as instructed in Dsixda Kitchen's thread but the problem was when u should Browse to where the Packages locally located to install from.
I used to not play around with browse to manually browse for the packages.. so now I decided to give it a try and it worked now..
instead of allowing the installation setup determine the default location for the packages I browsed to where it's exactly located... and just then now I can see the packages to install.
the default location will look like this:
D:\kitchen\dsixda_cygwin_install\
so u just then hit Browse and browse to this location this time and it'll work:
D:\kitchen\dsixda_cygwin_install\cygwin_packages
thats it for fixing the: NO PACKAGES FOUND problem, and it'll work with any windows system.
About Cygwin
Guys/Sir Im flashing my old firmware back using Odin v.3.. uhm why is it i can't write something in cygwin.bat? what will i do?
ooh my phone is Galaxy S5830i
or Please PM me i need the answer so badly .

[Tool][Linux] bptool v 2.0 - build prop updater for ROM Chefs

One thing that I have found to be very annoying is adjusting the build.prop file after making edits to the my ROM projects. Because of this I wrote a simple little script to update the build.prop to reflect changes before I build a new flashable.zip
This tool allows you to:
* rename your ROM
* change the product model /device
* update build date, build date UTC, and build incremental version
Place the file bptool in your ~/bin directory or a directory that is in your path and make sure it is executable.
Navigate to your ROM working directory system folder (ex: ~/working_directory/system) and from the terminal execute "bptool"
{
"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"
}
you can get the latest version here: https://github.com/OldSoldier/bptool
For your convenience I've attached the latest version of the script
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
oldsoldier2003 said:
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
Click to expand...
Click to collapse
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
cascio97 said:
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
Click to expand...
Click to collapse
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
oldsoldier2003 said:
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
Click to expand...
Click to collapse
It works. Sorry for not trying before leaving a comment. :crying: Thank you for your work.
updated to include the option to change productmodel / device name and fixed bug where the file was not properly updated if you run the same option more than once in a session.
v2.0 released
Cleaned up and commented code
added view prop settings option
added error handling

[TOOL][LINUX] AD Tools: apktool, signapk and smali/baksmali v1.0.0 [08 May 2016]

AD Tools - Linux
Android Development Tools for Linux
{
"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"
}
Well, I just found my self needing a tool for Linux wich could help me to decompile/recompile my files (apks, dex, jars... etc) so I looked for it but had no luck. Then I said: Ok, if I need it then I'm going to do it! I has been REALLY usefull to me, I hope it can also be usefull to all of you.
Introduction
AD Tools is a very simple but usefull tool to help you with everything related to apks, dex or jars modifications. It includes every function needed: decompiling, compiling, signing... etc.​
Usage
Here are some simple instructions to correctly use AD Tools:
Open AD Tools folder in Terminal and execute the 'ADTools' script.
To execute a script in terminal run this command:
Code:
./script
In our case it would be:
Code:
./ADTools
If you can't execute 'ADTools' file run this command and try again.
Code:
chmod +x ADTools
Take into account AD Tools always uses 'builded', 'decompiled', 'input' and 'signed' folders. Avoid creating more folders to do not get confused.
'input' folder to place the files wich are going to be used. Eg: an apk to be decompiled or classes.dex to be baksmalied.
All decompiled/baksmalied files are found in 'decompiled' folder.
Every builded/recomiled/smalied folder is found in 'builded' folder.
Features
Apktool
Signapk
Smali
Baksmali
Autoscanning files to avoid writting file names
Downloads
AD Tools v1.0.0
Older versions:
AD Tools - AndroidFileHost
Credits
@SuperR. I used his ROM Kitchen script as reference for AD Tools​
XDA:DevDB Information
AD Tools, Tool/Utility for the Chef Central
Contributors
sebastiandg7
Version Information
Status: Beta
Created 2016-05-09
Last Updated 2016-05-09
FAQ and TIPS
PD: I want to hear you about bugs, function requests, improvements you may like... etc. The idea is to have a tool for users made by users. Hope you enjoy it.
nice tool thanks a lot , so far working good
#suggestions
1. adding work spaces and the ability to switch between them

Categories

Resources