Related
We've updated a bit....
Download Link: [Here]
We now have a complimentary app on the app store for this A4D App.
What is A4D?
The goal of A4D is for us to move beyond just N1 make it an all in one flashing/upgrading/android utility. We just added a ROM library with MD5s. We are not going to be hosting the actual ROMs by themselves so if you report a dead link, they will be taken down (after a number of reports). You can also add your own ROMs as well into the library.
The ROM library will be supported by both Android and Desktop App. We are rewriting the Desktop apps so that we can do all 3 platforms in one, Linux, Windows, and Mac. You'll love the layout of the app. That's all we can say for now.
Oh one more thing. The android app won the best android app award at the Mobile in the Middle Hack-a-thon over the weekend in Chicago (on 3/6/2010).
I would like you guys to try out the app and tell us feedbacks. Also feel free to add your own ROMs to the Database and tell us how we can make the DB better. There a number of features we are trying to add as well. But with our full time jobs... things are going a little slower than we wanted. Sorry.
Requirements to run the app on Android: Amon_RA's recovery. That's what we tested it with.
Reserved
Reserved for Future Updates / Changelog
Can't wait to see if this is fool proof.
Add md5 check. Make it in this way: user have to enter/copy-past md5 hashsum from forum/site. Program calculates md5 of image and says image is good or bad. Also you can disable flashing with out this check. ;-)
good idea. Will do that. That will help with flashing screwed up downloads.
Hi
Thank you for sharing the application.
Does it flash the radio too? I mean CyanogenMod has two files a radio ROM and a CyanogenMod ROM. Does it flash both of them to the phone?
Thanks.
Radio flash is in there we took it out. May do so in the next release but radio flashing is dangerous (can brick phones) so...
Hey Lwin,
Nice concept man, this is gonna prove very handy for many peeps.
You've come up trumps again
So, this is a desktop application?
Does it flash ROM's from your desktop or copy them over and just run the commands on the phone for you?
I ask, as I'm having some problems flashing now, based round a slightly faulty Micro SD card. Does it store backups on the phone or on your desktop PC?
This program is written so you don't have to do command line commands. Everything else remains the same. If you are doing a Nand backup, it goes where it used to go.
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
nice app for those that aren't familiar with cmd or jus pure...lazy lol
maybe the screens should be bigger as quite hard to see clearly whats available.
Pure Genius...
seraph1024 said:
Here is the GUI tool for unlocking, updating, restoring, flashing of the N1 (and in theory should work on all HTC androids).
Try it out and see if it is useful. The tool is made to help for people with very basic skills since the tool at this stage is a wrapper for the shell commands at this point.
Again, as usual, we take no responsibility for loss of sleep, loss of phone or screw ups on our side (due to app) or on your side (due to lack of ability to follow instructions).
I wish to make it more simple. We welcome feed backs.
Seraph1024 - ShadowPyro
Download Link: [Here]
Click to expand...
Click to collapse
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
shadowpyro said:
This program is written so you don't have to do command line commands. Everything else remains the same.
Click to expand...
Click to collapse
But I don't use command line now. I didn't realise anyone did. Do you not just boot into RA Recovery and flash from there?
shadowpyro said:
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
Click to expand...
Click to collapse
Thanks, I didn't ask for advice.
GodDriven said:
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
Click to expand...
Click to collapse
There will be a mac port sometime this week. I can most likely port to linux too but if you know linux and if you have to use wrapper, you have an issue
install issues
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Sounds like the app uses .NET framework 3.5.
So goto microsoft website an get 3.5 .Net Framework.
pwvandeursen said:
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Click to expand...
Click to collapse
You do need .Net 3.5. It should have asked you, if not installed that as a prerequisite.
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
pwvandeursen said:
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
Click to expand...
Click to collapse
Can you send us a screenshot.
Do not unzip into C:\android-sdk-windows. App will install SDK or search for the SDK there.
Unzip on your desktop or temp and install from there.
just to be clear, I unzipped adroid sdk and placed in the mentioned location. the android4dummies is extracted on the desktop and executed from there..
so should I remove the SDK and retry?
Is there any way to change the white vibrant bootup logo? Where is this file located and would it be better to use a deodex rom to change this?
Thanks in advance
There's a lot of info on this. Try boot animation from the market. You need to be rooted BTW
is there a way to make my own bootanimation if I have a video file? or a pic?
Check tonicacids threads theres a tutorial on how to make them on his boot animation thread
This is not part of bootanimation.zip.
Its called a splash screen, and no I dont think u can change this yet, I think its hard coded into the kernel, but im no dev so not sure, I know u could on the g1 though
Sent from my SGH-T959 using XDA App
Check develop section. There was one thread about it I think
Sent from my SGH-T959 using XDA App
General FYI,
The Vibrant uses a 2-stage static splash screen, totally different from the traditional splash.img used on other android phones.
The first is called by the bootloader from the lfs partition, there's a thread in the development section on how to change this logo here: http://forum.xda-developers.com/showthread.php?t=947331
The second screen (in the case of the vibrant, this is identical to the lfs splash, so it seems like we only have one screen, but we don't, we still have two) is built into the kernel during compile.
There's a thread about this in the captivate section, with a specific post about the second splash here: http://forum.xda-developers.com/showpost.php?p=10851192&postcount=118
I tried playing with kernel dev today a little bit, but am having an awful time getting everything setup, even using existing, good kernel source like ttabbal's dragon kernel.
Anyway, hope this helps, cheers, =)
Its here...
http://forum.xda-developers.com/showthread.php?t=947331
Edit: Oops awesome Jocelyn explained it already.
Thanks everyone for pointing in the right direction! I'm prolly gonna want to change both anyways but may not be able to change the splash cuz of my limited knowledge. Also where is the splash img located? Is there asn apk I have to decompile?
ps.- jocelyn I have seen you help so many people why is you thank meter stuck at 7?
aamir123 said:
Thanks everyone for pointing in the right direction! I'm prolly gonna want to change both anyways but may not be able to change the splash cuz of my limited knowledge. Also where is the splash img located? Is there asn apk I have to decompile?
ps.- jocelyn I have seen you help so many people why is you thank meter stuck at 7?
Click to expand...
Click to collapse
Hey again,
The first splash (the one called by the bootloader) is stored in the lfs partition, the first link I provided has a great video walkthrough on how to change it. Basically, you have to flash a new param.lfs to your phone that by default doesn't contain a logo_T959.jpg image.
Then you create your new logo, 480x800, and save as logo_T959.jpg, keep filesize small (the video mentions ~20k being the optimal size.) Then use his provided batch script to remount the lfs partition read/write, and push the new logo to the phone.
The second image is vastly harder to change, since it has to be compiled into a kernel. The second post I linked to contains a walkthrough to make the image, but you then still need kernel source, and a build environment setup to compile your custom kernel with your splash screen.
Basically, you have to use GIMP to save your logo as "C Source Header" and then run a shell script to convert it into the proper samsung logo format, drop it in your /kernel/drivers/video/samsung directory, and compile the kernel.
Sorry, I've not been able to configure a build environment yet to successfully build a kernel (even from known good source, like ttabbal's dragon kernel) on my OSX partition, and I'm too stubborn to triple-boot mac/win7/ubuntu again.
Oh, and my thanks meter is low because I haven't posted much here since it was implemented, the lack of credit/thanks burned me out on android and xda-dev for a couple months.
Hope this helps, cheers, =)
s0niqu3 said:
Hey again,
The first splash (the one called by the bootloader) is stored in the lfs partition, the first link I provided has a great video walkthrough on how to change it. Basically, you have to flash a new param.lfs to your phone that by default doesn't contain a logo_T959.jpg image.
Then you create your new logo, 480x800, and save as logo_T959.jpg, keep filesize small (the video mentions ~20k being the optimal size.) Then use his provided batch script to remount the lfs partition read/write, and push the new logo to the phone.
The second image is vastly harder to change, since it has to be compiled into a kernel. The second post I linked to contains a walkthrough to make the image, but you then still need kernel source, and a build environment setup to compile your custom kernel with your splash screen.
Basically, you have to use GIMP to save your logo as "C Source Header" and then run a shell script to convert it into the proper samsung logo format, drop it in your /kernel/drivers/video/samsung directory, and compile the kernel.
Sorry, I've not been able to configure a build environment yet to successfully build a kernel (even from known good source, like ttabbal's dragon kernel) on my OSX partition, and I'm too stubborn to triple-boot mac/win7/ubuntu again.
Oh, and my thanks meter is low because I haven't posted much here since it was implemented, the lack of credit/thanks burned me out on android and xda-dev for a couple months.
Hope this helps, cheers, =)
Click to expand...
Click to collapse
Yea but alot of what you said sounds like chinese. Ill give it a try and it seems too hard its best left alone I guess. And your one of the best on these forums thanks for everything.
Hey guys,
So, as I've finally started test out all the different ROMs on this forum (and on others) for the HTC Amaze, I've also begun to develop specific debloater tools for each one. Eventually of course my goal is to create my own ROM, but seeing as how I'm still learning a lot of the developing techniques, it's going to be a while. But, as a minimalist, and an Android purist, most of the apps that comes with the Amaze is, at least to me, crap. There are some useful apps developed by HTC, but not many, and 95% of them I can live without (or replace with a Google or 3rd party app that works just as well or better).
I'm rambling, I know, sorry. But to get to the point, I plan on releasing a customized Debloater tool for most ROMs already developed on this forum and others. The first ROM I developed this debloater tool for was XBoarder's Bulletproof, which most of you already have seen (that thread will be linked to later on).
Of course, proper credit must be given where proper credit is due, and I will never develop a customized debloater for a ROM without giving credit to it's respective developer. But, seeing as how these Debloater tools don't actually borrow anything developed ROM, and are simply customized to work better with them (rather than say a one-size-fits-all tool), I do plan on taking credit for developing them. So please don't steal them and re-use them in an app or one-click tool without giving proper credit, because I do take my own personal time to do this. Thanks.
REQ's:
1. ClockworkMod 5.5.0.4 (or later) or HTC Sync and HTC drivers installed on PC.
2. The ROM for which you are downloading the specific Debloater.
3. Android SDK installed and system variables are set properly on your Windows machine (btw this won't work for linux, that may come a bit later). Instructions for this are found in the quote below. Copied straight off'a Cyanogenmod Wiki. Adjust folder paths to your android-sdk folder as necessary.
Go to the Control Panel, and select the System Properties (Windows XP) or System (Windows Vista/7).
Select the Advanced settings;
Windows XP: Click on the Advanced tab.
Windows Vista/7: Click on Advanced system settings on the left.
Click on Environment Variables.
Under the "System variable" section, you will look for "Path". Double-click on it.
In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk\platform-tools;C:\android-sdk\tools
Click to expand...
Click to collapse
CWM RECOVERY INSTALL INSTRUCTIONS
1. Plug into PC via usb.
2. Boot phone into recovery.
3. Select Mounts & Storage, then select 'Mount /System'.
4. Download attached .zip file with your PC, unzip to wherever.
5. Run the .bat file with the 'CWM' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
6. Reboot phone.
7. Done
HTC SYNC INSTALL INSTRUCTIONS
1. Plug phone into PC via USB, change connection type on phone to HTC Sync.
2. Wait for phone to find HTC Sync on PC.
3. Download attached .zip file with your PC, unzip to wherever.
4. Run the .bat file with the 'Sync' ending. I put several pause commands in the file, so if you come up with some errors you can just copy them straight from command prompt and paste them here.
5. Reboot phone
6. Done.
DISCLAIMER:
I claim no responsibility for anything this does lulz
No but seriously, this should work fine without causing any damage to your phone. I've tested it multiple times already. That being said, if it does f up your phone, I have no obligation to fix it. Use this at your own risk.
DOWNLOADS:
Bulletproof v2.5 Debloater & Debloater-Remover (All credit to XBoarder for this amazing ROM)
LINK to Thread
Stock Sense RUU (T-Mobile USA) Debloater & Debloater-Remover
DOWNLOAD
BeastMod 2.3 (Credit to XBoarder)
Coming Soon!
CHANGELOG:
Stock Sense RUU (T-Mobile) Debloater
v1.0 - Initial Release
Bulletproof v2.5 Debloater
LINK to Thread
NOTES:
Stock Sense RUU (T-Mobile)
After running the tool, you may get an error/fc message on your phone about the system app malfunctioning. This is normal. Just restart your phone (or if neccessary remove & re-insert the battery), and the messages will disappear.
Your tool looks real cool. Would it be possible to write a list of the programs it deletes?
realitysconcierge said:
Your tool looks real cool. Would it be possible to write a list of the programs it deletes?
Click to expand...
Click to collapse
Sure. Tell ya what, I'll include a README.txt file in the next update that lists which apps it removes.
This is a simple tool/script used to:
1. convert .jpg .png and .bmp files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Mac running OSX 10.9.1 (Mavericks), but should work on any OSX Mac
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png, jpg or bmp image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your Mac.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
NOTE: At this time this does not support having more than one of the same image type in the "place-image-here" folder when converting and flashing. A fix for that is already being worked on, but didn't see it as a major issue right now since you can only flash one splash screen anyway.
NEW NOTE: I was finally able to get the multiple images in one folder working and have implemented it only for .png images (other file types coming with next version). So now you can dump multiple .png files in the folder and the program will create the boot images, name them using the original filename and move them to the "images" folder. The next part of this to figure out is how to select your screen size and create a boot image of that size. Stay tuned...not that it seems many people are tuned, but that's OK.
NOTE: VERSION 1.2 - Removed support for .jpg and .bmp files. Didn't see the need to support multiple file types. There is now a Photoshop template file included with the script. Just open in photoshop and add your image to the top layer (labeled as "Team Logo" because I am using that as my template for my sports teams splash screens). If your image is large and covers the HTC and Beats logos (and you want them in your splash screen), just move the layers around how you want them. The colors of the HTC letters can also be changed however you want.
RESERVED
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
drakemata said:
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
Click to expand...
Click to collapse
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
I don't typically work with Windows, either...but I know there us still a large demand for making things easier for Windows users since a great majority of them are not as inclined to do stuff at the command line.
As long as there is one person interested, I will continue to work on this. Thanks for your reply.
Mav3rick40 said:
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
drakemata said:
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
Click to expand...
Click to collapse
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Mav3rick40 said:
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
Ok cool. Yeah I'm going to school for programming.
Sent from my HTC6435LVW using Tapatalk
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Mav3rick40 said:
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Click to expand...
Click to collapse
You need to navigate to it from the terminal and do ./splash_flasher.sh
Sent from my Droid DNA using Tapatalk
I figured it out after playing around with it for a couple of hours.
Sent from my HTC6435LVW using Tapatalk
Glad to see you figured it out. I am trying to convert this over to an Applescript app as well as working on my Linux version and making new splash screens for all sports teams (which was a much bigger undertaking than I thought it would be).
If you have any suggestions for improving the script or for additional tools that should be added, I would appreciate the feedback.
Drawing from the impressive work of CrashXXL in rooting our phones, jahrule in simplifying the process, and Sabissimo in developing a tutorial to bake in apps for those of us with locked bootloaders and write protected systems, I have with great effort arrived at this glorious day. I present to thee: Suicide Flash.
What is Suicide Flash? It is a collection of Bash scripts and other files which streamline and automate the process of using the Qualcomm emergency download mode (Qualcomm HS-USB QDLoader) to write to the system partition on Moto phones using MSM8960 processors. It applies the method used to root these devices (see here, for example) to the task of arbitrary system modification. In other words: Suicide Flash makes it easy(ish) to modify system files for those of us who can't use traditional methods.
Code:
DISCLAIMER: This is obviously a dangerous tool. I mean, it
flashes your phone by bricking it first. Be smart. I shan't be held
responsible if your phone melts, explodes, loses all of its data,
or cheats on you with a hula dancer.
Who Can Use It?
Suicide Flash is for sure compatible with most Moto X variants. The testing has been done primarily with an XT1049, the Republic Wireless model, but has also included the XT1060 (Verizon) and should work on most/all of them. However, in theory any phone, or at least any Moto phone, using the MSM8960 chip could be compatible, such as the Droid Turbo. So to simplify:
XT1049 (Moto X Republic Wireless): Tested and working
XT1060 (Moto X Verizon): Tested and working
XT1058 (Moto X AT&T): Untested, highly likely to work
XT10XX (Any other Moto X): Untested, likely to work
Others: Untested, may work as long as they use MSM8960
How Do I Use It?
Suicide Flash (SF) consists of three main scripts: a flashing script, a package creation script, and a pushing script. Details:
suicideflash.sh: Flashes SF packages to the phone in bricked (QDLoader) mode
pkgmaker.sh: For developers. Creates SF packages from system images.
suicidepush.sh: Uses the SF system to "push" system files in an ADB-like way
To use these scripts, simply extract them to a place of your convenience. All scripts must be run from the root Suicide Flash folder. Do not run any of them from within the "scripts" folder. Also, while it may not strictly be necessary, it is best (if you are developer) to include any relevant system images in the root Suicide Flash folder, as well.
As an end user, you can download SF packages created by developers and flash them using the main Suicide Flash script. As a developer, you can pull system images and use them to create SF packages with the pkgmaker.sh script. Anyone can feel free to use the Suicide Push script to push files to their device. For more information, here are the help pages for each.
Suicide Flash:
Code:
Usage: suicideflash.sh PACKAGE
Flashes PACKAGE to the system parition of a Moto phone using Qualcomm
emergency download mode.
Options:
-h, --help displays this help message
-s, --skip skips all prompts and runs without user interaction
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
Package Maker:
Code:
Usage: pkgmaker.sh [OPTION]... ORIGINALSYSTEM TARGETDEVICE REQUIREMENTS
SYSTEMOFFSET OUTPUTFILE
Creates a Suicide Flash package for writing to Moto phones via the emergency
Qualcomm download mode.
Arguments:
ORIGINALSYSTEM provides the original system image to be modded
TARGETDEVICE specifies the model of phone for the package to flash
REQUIREMENTS notes any important requirements for the phone state
prior to flashing
examples: "Stock", "Rooted", or "Rooted+Xposed"
SYSTEMOFFSET the address of the system partition on the target device
should be in hex format (i.e. 0x6420000 or 6420000)
can use value ADB to pull the offset over ABD
OUTPUTFILE the name of the Suicide Flash zip package to be created
Options:
-h, --help returns this help message
-m MODDEDSYSTEM specifies an existing modded system image
if not given, will mount original for modification
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
Suicide Push:
Code:
Usage: suicidepush.sh LOCALFILE REMOTEFILE
Uses Suicide Flash to push LOCALFILE to a phone system at REMOTEFILE.
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
What Do I Need to Use It?
A Linux installation
ADB
Fastboot
Rhino
Python
A package called python-serial
VirtualBox
ADB Insecure (if developing or using Suicide Push)
If you don't have some of these (except, obviously, the first one and the last one), you can run the included script install-tools.sh. It will automatically install anything you're missing.
Okay, Give Me Step-By-Step Instructions
For End Users:
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Download an SF package from a developer for your device
Flash the package with the command:
Code:
./suicideflash.sh DOWNLOADEDPACKAGE.zip
Profit!
For Developers:
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Pull a system image from your phone
Run pkgmaker.sh to create an SF package
Upload the package for the benefit of others
For Anyone, to Use Suicide Push
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Push files to your phone's system partition with this command:
Code:
./suicidepush.sh LOCAL_SOURCE /system/PUSH_DESTINATION
So, What Can I Do with It Right Now?
If you're a developer, you can get to work creating SF packages for your device. If you're just a plain ol' user, there's not much to be done until others chip in. I have uploaded one package as a sample and for the convenience of anyone looking to root their XT1049 and install Xposed. I will maintain a master list of uploaded packages as people make them.
XDA:DevDB Information
Suicide Flash for Moto, Tool/Utility for the Moto X
Contributors
Nicene Nerd, CrashXXL, Sabissimo
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2015-08-07
Master Package List
XT1049: Republic Wireless Moto X
- root-xposed-xt1049-4.4.4.zip: Root and Xposed for XT1049. Requires stock 4.4.4 from SBF, not OTA.
- busybox-xt1049-rooted-xposed-4.4.4.zip: BusyBox for XT1049. Requires 4.4.4 rooted w/ Xposed.
XT1058: AT&T Moto X
- root-xt1058-4.4.4.zip: Root for XT1058 KitKat. Requires stock 4.4.4 from SBF, not OTA.
- xposed-xt1058-rooted-4.4.4.zip: Xposed for XT1058 KitKat. Requires rooted 4.4.4.
- root-xt1058-5.1.zip: Root for XT1058 Lollipop. Requires stock 5.1 from SBF, not OTA.
XT1060: Verizon Wireless Moto X
- root-xt1060-4.4.4.zip: Root for XT1060. Requires stock 4.4.4 from SBF, not OTA.
- xposed-xt1060-rooted-4.4.4.zip: Xposed for XT1060. Required rooted 4.4.4.
Changelogs:
08/07/2015 - v0.2
- suicideflash.sh: Increased wait period before giving error on not finding phone in emergency mode
- mountimg.sh: Fixed issue which would cause errors preventing images from mounting
- pkgmaker.sh: Added option to pull system image over ADB, improved error handling
Developer pkgmaker.sh Tutorial: Creating an Xposed Framework Package
Say you want to make a package that installs the Xposed framework, since that requires writing to /system. Here's how you would do it with Suicide Flash (assuming you have already rooted the phone):
Open a terminal window to your Suicide Flash root folder. Then sudo su.
Pull a system image. One way to do that:
Code:
adb root
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/system /sdcard/originalsystem.img bs=1024
adb pull /sdcard/originalsystem.img
Run the pkgmaker script like this, assuming you're using a rooted XT1049 on 4.4.4, but you don't know the offset of the system partition, so you want to pull it via ADB. The script will be placed in output/xposed-flash-package.zip.
Code:
./pkgmaker.sh originalsystem.img XT1049 "Stock 4.4.4" ADB xposed-flash-package.zip
The script will pause when originalsystem.img is mounted for writing. As root, copy the Xposed app_process file (which you can extract from the APK if you need it) to "mnt-originalsystem.img/bin/app_process". Then press enter.
The script will continue executing, hopefully without errors.
Voila! Your package xposed-flash-package.zip is ready to upload and/or flash.
Finally!
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Also, if you have it tested and everything with Republic, I would appreciate a torrent or hosted file somewhere. If there isn't one before I finish, I'll post it.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Cindex said:
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Also, if you have it tested and everything with Republic, I would appreciate a torrent or hosted file somewhere. If there isn't one before I finish, I'll post it.
Click to expand...
Click to collapse
Sorry for the double post but I can't edit yet, just realized that the zip file there is all that's needed for Republic. I was going to post the ADB/USB driver setup link for linux, but I'm not allowed yet.
Cindex said:
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Click to expand...
Click to collapse
You shouldn't need to do anything special for Linux drivers. It works straightforwardly as long as you have fastboot and ADB. The flashed file that creates the softbrick is included by the package maker script in every Suicide Flash package, so it is easy to unbrick. In fact, I can upload another package just for unbricking if you'd like.
Added a BusyBox package for XT1049, and added root and Xposed packages for XT1060.
Edit: also added root packages for XT1058 on both KitKat and Lollipop, plus Xposed for XT1058 KitKat.
Nicene Nerd said:
You shouldn't need to do anything special for Linux drivers. It works straightforwardly as long as you have fastboot and ADB. The flashed file that creates the softbrick is included by the package maker script in every Suicide Flash package, so it is easy to unbrick. In fact, I can upload another package just for unbricking if you'd like.
Click to expand...
Click to collapse
That's good to know, I looked around and couldn't find anything on the driver for the Qualcomm Emergency Download mode. I suppose not needing one would be why. Actually some kind of emergency package to unbrick might be good. Now that I see the script in there I don't have a problem, but someone might like it.
So now I'm wondering if I actually have to do a factory reset again, or if I can just flash the SBF file itself and not have to wipe. I'm not sure how big of a difference there is, because I did the factory restore recently and the OTA update was like 6MB or something. I wouldn't think there's be an issue flashing it rather than factory restore. Any ideas?
Also, if anyone knows a good way to do this with Virtualbox it would be a nice addition. I'm personally not going to bother since I already have a bootable Ubuntu USB, but it seems that most people would rather set up a VM with a small linux distro. If it had the tools baked in, it would make it an easy process.
Cindex said:
That's good to know, I looked around and couldn't find anything on the driver for the Qualcomm Emergency Download mode. I suppose not needing one would be why. Actually some kind of emergency package to unbrick might be good. Now that I see the script in there I don't have a problem, but someone might like it.
So now I'm wondering if I actually have to do a factory reset again, or if I can just flash the SBF file itself and not have to wipe. I'm not sure how big of a difference there is, because I did the factory restore recently and the OTA update was like 6MB or something. I wouldn't think there's be an issue flashing it rather than factory restore. Any ideas?
Also, if anyone knows a good way to do this with Virtualbox it would be a nice addition. I'm personally not going to bother since I already have a bootable Ubuntu USB, but it seems that most people would rather set up a VM with a small linux distro. If it had the tools baked in, it would make it an easy process.
Click to expand...
Click to collapse
Technically, the only reason for the SBF is because when you install OTA updates, files may end up in slightly different positions depending on the circumstances. For this to work, you must start with an identical system partition to the one used for making the package. So all you need to really do is extract the system.img and flash it, if you wish. No data loss necessary.
Also, I'll look into a minimal VM. I thought about actually trying to make a Windows version of Suicide Flash. I'm not sure which I'll end up with.
So I tried this on my Ubuntu 12.04.5 last night, and it didn't recognize the device in fastboot. I'm going to try on Ubuntu 15.04 soon here. Another question for you though, which sdk do I use for XPosed? I don't seem to be able to figure it out searching all over. I would think 16, but maybe it's for Lollipop?
I think I'm going to get some of these with the OTA, it'll make it easier for the average Republic user once it's gotten going.
Cindex said:
So I tried this on my Ubuntu 12.04.5 last night, and it didn't recognize the device in fastboot. I'm going to try on Ubuntu 15.04 soon here. Another question for you though, which sdk do I use for XPosed? I don't seem to be able to figure it out searching all over. I would think 16, but maybe it's for Lollipop?
I think I'm going to get some of these with the OTA, it'll make it easier for the average Republic user once it's gotten going.
Click to expand...
Click to collapse
I can't answer your Xposed Lollipop question. I was wondering the same thing, but I ended up simply pulling the file from an existing Xposed installation. I suppose you could do the same and then diff the files to find out which is correct.
As for the OTA, that's not possible. Every time an OTA is installed, the files can end up in different places on the flash memory, and this utility requires knowing the exact locations for making changes. You'd have to make separate packages for every phone. Otherwise you'll end up with bootloops.
Has anyone tried using Suicide Push? It's slow, but I thought it would be the more celebrated part of this since it lets you do basically the same as an ADB push to the system partition. You could even install Xposed that way:
Code:
./suicidepush.sh local_app_process_file /system/bin/app_process
Nicene Nerd said:
Has anyone tried using Suicide Push? It's slow, but I thought it would be the more celebrated part of this since it lets you do basically the same as an ADB push to the system partition. You could even install Xposed that way:
Code:
./suicidepush.sh local_app_process_file /system/bin/app_process
Click to expand...
Click to collapse
I'm still working on getting it to root. I was going to a few days ago, but my flash drive burned out. I'm going to try Ubuntu 14.04.3.
What linux distro did you use?
---------- Post added 14th August 2015 at 12:41 AM ---------- Previous post was 13th August 2015 at 11:47 PM ----------
Sorry to double post again, but I can't edit yet and have a few more things. I can't seem to be able to find a RW SBF file. I'm thinking restore from factory sounds like a good solution, but I don't know if that's the same thing.
How can I pull a system image if I'm not root? Without an SBF file, I need to package it for myself. Without root, I can't pull the system.img. I'm sure others on networks not covered yet would like to know also. Where did you get your system.img?
Also, if we can get this deep, and you can modify the bootloader, couldn't you just flash the old bootloader image and then the rest of the ROM? Then we could unlock the bootloader using older methods. We might have to flash block by block, but it should work?
Cindex said:
I'm still working on getting it to root. I was going to a few days ago, but my flash drive burned out. I'm going to try Ubuntu 14.04.3.
What linux distro did you use?
---------- Post added 14th August 2015 at 12:41 AM ---------- Previous post was 13th August 2015 at 11:47 PM ----------
Sorry to double post again, but I can't edit yet and have a few more things. I can't seem to be able to find a RW SBF file. I'm thinking restore from factory sounds like a good solution, but I don't know if that's the same thing.
How can I pull a system image if I'm not root? Without an SBF file, I need to package it for myself. Without root, I can't pull the system.img. I'm sure others on networks not covered yet would like to know also. Where did you get your system.img?
Also, if we can get this deep, and you can modify the bootloader, couldn't you just flash the old bootloader image and then the rest of the ROM? Then we could unlock the bootloader using older methods. We might have to flash block by block, but it should work?
Click to expand...
Click to collapse
I used Ubuntu 14.04.
The RW 4.4.4 SBF can be found here or here. It does not appear possible to pull a system image without root. But even without permanent root, KingRoot can get you temp root long enough to pull a system image.
As for the bootloader, there's certainly a chance that this could be done. It's just so risky that I won't try it myself. If there was a single variable missed, it could easily mean hard-brick. But in theory, as far as I understand, it might work. The biggest obstacle might be partition changes. If you got the bootloader to get into fastboot mode, though, you could presumably fix that with an old SBF.
Flashing the olderer bootloader will not work (I have tried and confirmed it does not work). It is because the efuses verify the bootloader.
Wow! That's hell of a tool you've created here Awesome job! I haven't tried it myself yet, but, judging by source code, it should get the work done. More of a developer tool, ofc, but it's more then impressive Maaan, I wish there was a normal way to work with ext4 partitions to make it available on Windows))
Since you've made "push" version of it (and that's the most interesting part, longest though), the next step in future development should be doing the same with TWRP flashable zips. Some of them just put apk-s in system folder, some of them have shell scripts inside, I've yet to figure out the pattern But that would be awesome next step to this awesome project
download link not found )
theres a tool bar at top crash with download links next to discussions and screenshots
Sabissimo said:
Wow! That's hell of a tool you've created here Awesome job! I haven't tried it myself yet, but, judging by source code, it should get the work done. More of a developer tool, ofc, but it's more then impressive Maaan, I wish there was a normal way to work with ext4 partitions to make it available on Windows))
Since you've made "push" version of it (and that's the most interesting part, longest though), the next step in future development should be doing the same with TWRP flashable zips. Some of them just put apk-s in system folder, some of them have shell scripts inside, I've yet to figure out the pattern But that would be awesome next step to this awesome project
Click to expand...
Click to collapse
I've actually started work on a Windows version, but it's on back burner because school just started. Here's a hint, though: with OSFMount and Ext2Fsd, you can mount Moto system images (pulled from the phone, not SBF ones) as hard drives or removable disks. Suicide Flash for Windows will rely on them.
So what are the chances I could use this to pull a system.img, and actually go in and delete some apps out of my XT1058? I had some success but it pulled the image as a mbn and I'm hesitant to try flashing it.
lpjunior999 said:
So what are the chances I could use this to pull a system.img, and actually go in and delete some apps out of my XT1058? I had some success but it pulled the image as a mbn and I'm hesitant to try flashing it.
Click to expand...
Click to collapse
Here's what you'll want to do:
Create the system image on the phone with
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/oldsystem.img bs=1024
ADB pull or MTP copy the image to your PC.
Run pkgmaker.sh like so:
Code:
./pkgmaker.sh oldsystem.img XT1058 "My System" 4B000000 modded-system.zip
When prompted, you can delete apps as root from the mounted system image under mnt-oldsystem.img/app or mnt-oldsystem.img/priv-app
Continue and finish the script.
Flash with
Code:
./suicideflash.sh -s output/modded-system.zip