[ TOOL ] CWM Update Binary - Optimus One, P500, V General

Ok folks. I've put together a Python/wxPython utility that will automate changing the update-binary in KitKat ROMs to a update-binary that is suitable for older recoveries. This will allow the older recoveries to install KitKat ROMs without having to juggle multiple recoveries.
This particular tool was written specifically for the LG Optimus One device family ( P500 and variants ). This utility will NOT manipulate anything other than an Android 4.4+ ROM for a p500 or thunderg board.
Users of other devices that may be interested in this utility for their device, please feel free to contact me via PM. As of now tho my intended audience is the LG Optimus One family.
[ Download ]
Windows users need Python 2.7.6 and wxPython 2.8 installed on their PCs before trying to use this tool. I am working on a Windows only version as well.Linux/Ubuntu :: CWM_UpdateBinary_1.0.0.zip​

Reserved

Can I use in TWRP 2.6.3.0 to flash 4.4 ??

Cool, many thanks!
I am so happy to get rid of hardware button-based cwm for better recovery

z1022 said:
Can I use in TWRP 2.6.3.0 to flash 4.4 ??
Click to expand...
Click to collapse
Should be able to.
Sent from my LG-P769 using Tapatalk

EDIT: Nevermind, I answered my own question.
Thanks for this tool. You are always helping us.
Sent from my LG-P500 using Tapatalk 2

ibub said:
EDIT: Nevermind, I answered my own question.
Thanks for this tool. You are always helping us.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
More than happy to. I'll never be a professional programmer but I don't want to let what I've learned go to waste.
Sent from my LG-P769 using Tapatalk

shinobisoft said:
Windows users need Python 2.7.6 and wxPython 2.8 installed on their PCs before trying to use this tool.
Click to expand...
Click to collapse
Tried on Windows XP x86, when pressing Update program silently crashes, binary doesn't replaced.
Python 2.7.6 and wxPython 3.0 installed, trying this 4.4 build.
z1022 said:
Can I use in TWRP 2.6.3.0 to flash 4.4 ??
Click to expand...
Click to collapse
When I replacing binary from tool manually TWRP 2.6.3.0 and CWM 5.0.2.0 still failed to install rom (Status 6).
What needs more to do?
--------------------------------
shinobisoft said:
I am working on a Windows only version as well.
Click to expand...
Click to collapse
Utility can be greatly simplified if use command line version of 7Zip. It can replace files in archive.
If it's really necessary (?) checking build.prop can be implemented though internal find command.
Simple BAT/CMD file and not needing additionally install large Python environment if Windows-version still will be based on it.
So here's attached simple standalone working script of that I talking for.
Extract, place ZIP into "1 Place ZIP here" folder, launch "1 Start.bat", grab file from "2 Done" folder.
Script checking line ro.build.version.release in build.prop. Written 4.4, but 4.4.* passed too.
All this can be easily wrapped in GUI (AutoIt etc).

Bonoboo said:
Tried on Windows XP x86, when pressing Update program silently crashes, binary doesn't replaced.
Python 2.7.6 and wxPython 3.0 installed, trying this 4.4 build.
When I replacing binary from tool manually TWRP 2.6.3.0 and CWM 5.0.2.0 still failed to install rom (Status 6).
What needs more to do?
--------------------------------
Utility can be greatly simplified if use command line version of 7Zip. It can replace files in archive.
If it's really necessary (?) checking build.prop can be implemented though internal find command.
Simple BAT/CMD file and not needing additionally install large Python environment if Windows-version still will be based on it.
So here's attached simple standalone working script of that I talking for.
Extract, place ZIP into "1 Place ZIP here" folder, launch "1 Start.bat", grab file from "2 Done" folder.
Script checking line ro.build.version.release in build.prop. Written 4.4, but 4.4.* passed too.
All this can be easily wrapped in GUI (AutoIt etc).
Click to expand...
Click to collapse
I cannot say why the program fails on Windows XP x86 when pressing the Update button. I no longer own an XP machine to test on. I just updated my wxPython to the version you installed and it runs just fine. I'm at a loss. Sorry.
I appreciate your input, however I am a C/C++ programmer not batch script. The Windows stand-alone version has nothing to do with Python or wxPython. It is written in C at the API level so it's pretty small. I only mentioned installing Python and wxPython for those who may have been too impatient to wait for the Windows only version. Linux/Ubuntu OS's come with Python preinstalled.
Also, please bear in mind, I'm doing this on my dime and my time :silly: The Python version only took a few hours to write. The stand alone Windows version will take 4 times that long. GUI is done for the Windows version, I'm still having issues with my zip libraries.
I may also be missing something. I remember reading somewhere that the updater-script needs to be modified as well for this hack to work but I can't find any reference as to what exactly needs modified.

Windows XP x86, wxPython 3.0 will crash. use wxPython 2.8 is OK.
However, use TWRP 2.6.3.0 and CWM 5.0.2.0 still failed to install this rom (error Status 6).

Let me do a little more digging
Sent from my LG-P769 using Tapatalk

Had what I needed all along... Oops. Running a couple tests yet. Will let yall know when I upload the update

Not sure what exactly is going on here. I have two P500 KitKat ROMs, 12/27 and 12/31. Manually editing or using my tool to edit both end up with the same situation after installing the ROM. It won't boot. Not even LG logo. My P509 eventually reboots back to recovery. So... I'm at a loss. Could be my recovery too, although I'm pretty sure someone else has reported success manually editing the ROM and installing with CWM 5.0.2.7 Touch by @vivekkalady.
Any ideas?
EDIT:
I still can't get either ROM to boot. No problem installing either ROM edited either way, they just won't boot. Editing manually or with this tool. WT?... I've tried with 4 different recoveries too...

Related

[ONLINE ROM LIBRARY, GUI & Android TOOL for HTC PHONES]

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?

[SCRIPT] Bloatware/Boot Animation and Sound Removal Script | Team Fireballas

A Team Fireballas Release
Requirements:
ROOTED HTC Droid Incredible 4G LTE, Stock ROM
TWRP or CM Recovery
External SD Card
Windows
This was tested on Win 7, but should work on XP, Vista, or 7. A Linux version is possible if there is demand.
Instructions:
Perform a NANDROID backup in TWRP or CM Recovery
Download and unpack bloat.v1.1.zip
Update bloat_list.txt as desired. The included list is intentionally short, and you may desire others to be removed.
Plug in phone and enable USB debugging
Double-click bloat.bat
Follow prompts
The script will reboot your device into recovery to make the needed changes, since some issues can occur if run while booted into system.
You might need to wipe cache afterwards, depending on what apps were removed.
This tool will remove system bloat apps in /system/app/, based on the bloat_list.txt file enclosed. It makes a backup of them in /system/app.disabled/.
It also can remove the DROID boot animation and DROID boot sound. Options are provided to perform any or all of these operations.
Please let me know what you think.
v1.1 Changelog:
Improved variable usage
Improved error-handling
Increased timeout while waiting for reboots
Added choice.exe to the .zip
Cleaned up whitespace
Portable version(Not tested but im 98% sure this will work)
This is portable version if anyone wants to try, all required is script manager which is found on play store to execute it
Requirements:
root
For it to work you have to click root icon on smanager
When downloaded remane it from mobile bloat.zip to mobile bloat.sh, otherwise it wont work
please report back
Didn't work for me. It says:
List of devices attached
HT26JS309742 device
'CHOICE' is not recognized as an internal or external command,
operable program or batch file.
Please attach your device and try again.
Press any key to continue . . .
Choice should be an included Windows batch command.
What version of Windows? I tested on Win 7 Ultimate, so I wonder if maybe you have a home or media center edition that doesn't have it. If that's it then I might need to rework this.
Sent from my ADR6410LVW using xda app-developers app
CaptainRewind said:
Choice should be an included Windows batch command.
What version of Windows? I tested on Win 7 Ultimate, so I wonder if maybe you have a home or media center edition that doesn't have it. If that's it then I might need to rework this.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on ultimate.
I will dig into this issue, thanks for letting me know.
Edit: It appears that it's actually part of the Windows Resource Kit.
I will see if it's possible to upload a new zip with it included. In the meantime, could you try installing that from Microsoft and let me know?
Sent from my ADR6410LVW using xda app-developers app
CaptainRewind said:
I will dig into this issue, thanks for letting me know.
Edit: It appears that it's actually part of the Windows Resource Kit.
I will see if it's possible to upload a new zip with it included. In the meantime, could you try installing that from Microsoft and let me know?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I copied choice.exe from windows\system32 to the bloat folder and it worked!
But then I got this:
/sbin/sh: /sdcard/nativeBloat.sh: not found
Removing bloat.
mv: can't rename '/system/app/HtcOMADM_SettingsPlugin_VZW.odex': No such file or
directory
mv: can't rename '/system/app/HtcOMADM_VZW.odex': No such file or directory
mv: can't rename '/system/app/TetheringGuard.odex': No such file or directory
Removing sound.
aaaaaaaand the boot animation is still there. Droid sound and bloatware were successfully removed, though.
reserved for later...!!Thanks
jtdogblue said:
I copied choice.exe from windows\system32 to the bloat folder and it worked!
But then I got this:
/sbin/sh: /sdcard/nativeBloat.sh: not found
Removing bloat.
mv: can't rename '/system/app/HtcOMADM_SettingsPlugin_VZW.odex': No such file or
directory
mv: can't rename '/system/app/HtcOMADM_VZW.odex': No such file or directory
mv: can't rename '/system/app/TetheringGuard.odex': No such file or directory
Removing sound.
aaaaaaaand the boot animation is still there. Droid sound and bloatware were successfully removed, though.
Click to expand...
Click to collapse
Had you previously removed those apps listed manually? Also what recovery are you running?
Basically, the .bat is a wrapper for a script that runs natively from recovery I wrote last year for the OG Incredible. It basically just copies two files, then kicks off the script from recovery based on the options you chose. I think now that it might be better for me to simply port all the logic into the parent .bat script, add choice.exe to the zip, and update the OP. This will have the bonus of eliminting the requirements for the resource kit and an sd card.
Will work on that.
Also I think the very first error is a race condition, so maybe 90 seconds isn't long enough to reboot into recovery. This would explain why the animation didn't change but the others did, since I went alphabetically so animation is executed first. Will increase timeout and gracefully handle absence of those .odex files or any others on the list not on the system.
Here is an advantage to the native .sh script, too, since checking for existence of a file on the android system would be really clunky and unreliable from a .bat file. I will try these things before a re-architecture of where the core logic lives. We are already stretching the limits of what Batch can do which is why I used native .sh script to do most of the real work.
Sent from my ADR6410LVW using xda app-developers app
jtdogblue, I've uploaded a v1.1 to the OP, mind trying it?
CaptainRewind said:
jtdogblue, I've uploaded a v1.1 to the OP, mind trying it?
Click to expand...
Click to collapse
Worked like a charm
Removing animation.
Removing bloat.
Removing sound.
==============================================
Rebooting and sleeping for 120 seconds.
Wait 120 seconds, or click c to continue once rebooted.
==============================================
==============================================
Removing script files from device, please standby.
==============================================
Press any key to continue . . .
jtdogblue said:
Worked like a charm
Removing animation.
Removing bloat.
Removing sound.
==============================================
Rebooting and sleeping for 120 seconds.
Wait 120 seconds, or click c to continue once rebooted.
==============================================
==============================================
Removing script files from device, please standby.
==============================================
Press any key to continue . . .
Click to expand...
Click to collapse
Great! Thanks so much for the valuable feedback!!
is there a full list of the bloat
for example
if I don't use twitter (or sence's twitter) what can I remove
if I use a different launcher then I cant use the sense widgets. which ones are those
dcooterfrog said:
is there a full list of the bloat
for example
if I don't use twitter (or sence's twitter) what can I remove
if I use a different launcher then I cant use the sense widgets. which ones are those
Click to expand...
Click to collapse
This remove Verizon bloatware if I'm right, if you wanna remove all of apps you don't use , unlock your bootloader, flash recovery and flash team venoms rom
Sent from my HTC Fireball using xda premium
i am not sure I want to flash a different rom this is my every day phone. I had some issues in the past on other phones
also I would rather remove the stuff myself.
i got rid of the obvious stuff lets golf....
i have frozen a BUNCH OF STUFF and will probably remove it slowly
I'm getting an error when I attempt to run this.. Not sure if its something I'm doing wrong.. Pretty much just download bloatv1.1, extracted, and run as admin for bloat.bat. Also when i checked the properties, I have to "unblock" each file extracted from the bloat.v1.1.zip, However this still did not fix the problem. I'm using windows 7 utl. x64.
C:\Users\quantum\Downloads\bloat.v1.1 (1)>echo off
==============================================
Written by CaptainRewind
Team Fireballas
Team Fireballas is jose51197 and CaptainRewind
==============================================
This script can remove Bloatware and Boot Animations
from the HTC Incredible 4G LTE.
You must be rooted, and have CM or TWRP recovery installed!
Your device must be connected to a USB 2.0 port!
==============================================
BACKUP COPIES OF ALL FILES WILL BE MADE.
==============================================
List of devices attached
(NAME OF DEVICE) device
This version of C:\Users\quantum\Downloads\bloat.v1.1 (1)\choice.exe is not comp
atible with the version of Windows you're running. Check your computer's system
information to see whether you need a x86 (32-bit) or x64 (64-bit) version of th
e program, and then contact the software publisher.
Please attach your device and try again.
Press any key to continue . . .
---------- Post added at 12:42 AM ---------- Previous post was at 12:08 AM ----------
quantumtransfer said:
I'm getting an error when I attempt to run this.. Not sure if its something I'm doing wrong.. Pretty much just download bloatv1.1, extracted, and run as admin for bloat.bat. Also when i checked the properties, I have to "unblock" each file extracted from the bloat.v1.1.zip, However this still did not fix the problem. I'm using windows 7 utl. x64.
C:\Users\quantum\Downloads\bloat.v1.1 (1)>echo off
==============================================
Written by CaptainRewind
Team Fireballas
Team Fireballas is jose51197 and CaptainRewind
==============================================
This script can remove Bloatware and Boot Animations
from the HTC Incredible 4G LTE.
You must be rooted, and have CM or TWRP recovery installed!
Your device must be connected to a USB 2.0 port!
==============================================
BACKUP COPIES OF ALL FILES WILL BE MADE.
==============================================
List of devices attached
(NAME OF DEVICE) device
This version of C:\Users\quantum\Downloads\bloat.v1.1 (1)\choice.exe is not comp
atible with the version of Windows you're running. Check your computer's system
information to see whether you need a x86 (32-bit) or x64 (64-bit) version of th
e program, and then contact the software publisher.
Please attach your device and try again.
Press any key to continue . . .
Click to expand...
Click to collapse
Bloatv1.0 worked just fine. btw.. not sure what i'm doing wrong with 1.1

{Script} Moto Milestone X2 2.3.6 Root

I have noticed that many people have had issues rooting their phone, especially recently. And i have also gotten tired of typing or copying the root method over and over after flashng in RSD and loosing root.
In response to that i have taken it upon myself to write a script for automating a majority of the process for all of us, making the process swifter than before. However this is not a one click root there are many steps nessecary to root our device. All i have done is wiritten a script to automate a majority of the process.
I will only test one version of the script, the ubuntu 12.10 version, because thats the only operating system i run and its easiest to test this one. i will leave the other versions to other people and to post issues with them as they arise so i may fix them
there are several versions of the script
*Ubuntu - 12.10 and up
*Ubuntu generic - 10.04-12.04
*Linux generic - any version of linux
*Windows bat file - Must download Motorola drivers
*Android - NEW ALPHA!! can actually be run from another rooted phone or tablet!! Scripts for general use coming soon! Testers are welcome! Check out the second post for details.
each version has the nessecary files to root your phone and including the script
These are not flash able scripts these must be uncompressed and run on a computer
Oh and feed back is more than welcome im not an expert at writing scripts or any sort of write up but i will do my best to fix any flaws or add suggestions.
Post 2: Change Log & Unstable Versions
Post 3: Instructions
Motorola USB drivers
Motorola website
MyGoogle Drive
Change log and unstables
Change log:
Version 4 - for windoze only:
Cleaned up script and readme
tested script runs into an issue because of the way windoze command prompt works
will update the instructions to inclued a sepereate method meant for windoze
Version 3:
Changed initial reboot command to adb reboot
broke script into to parts to fix adb shell /preinstall/su issue
Version 2:
Not published
would not get past adb shell /preinstall/su
Version 1:
First version made
BETAS:not for the faint of heart
To use you agree to contact me via pm upon downloading to obtain the password. This is because I REQUIRE all who use unstable versions to provide details and information on what does and does not work and what I can do to improve the experience.
MX2-arm-root:
Version alpha 0.1
Initial creation
No scripts
Root must be applied manually
Will need USB otg cable or micro USB to micro USB cable for fastboot command use (required cannot be fixed to run any other way)
Otg cable can be purchased for a few dollars from Amazon or other electronic retailer
MX2_arm_root_alpha0.1.zip
broken beyond android 4.1.2
Instructions:
*Download the zip file for your computers operating system from post one
*decompress with your favorite arcive manager i prefer 7zip
*READ THE README!!!!
*run initial script aka MX2-2.3.6-something-root
*follow instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*while your still in the adb shell as root run the following
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Windoze Instructions:
*decompress the zip and place somewhere easilly accessable by both windows explorer and command prompt
*READ THE README!!!!
*make sure drivers are installed- if at any point while the first script is running that drivers need to be installed(aka first time windoze has seen fastboot ect) wait for the drivers to finish installing before continuing.
*double click the initial script MX2-2.3.6-windows-root.bat
*follow the instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*close the script command prompt when finished
*open a new command prompt and do the following
*cd(to the directory where you uncompressed the zip
*adb shell
*/preinstall/su
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
there aren't any roms based on 2.3.6, doubt we will see any soon
Sent from my Milestone X2 using xda app-developers app
PotentChili said:
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
Click to expand...
Click to collapse
Try eclipse its not 2.3.6 based but it runs wonderfully on the mx2. As for the script its mostly an untested product. I've runt the Ubuntu 12.10 one once with little issue but the rest I haven't tried. Just remember its a two part script that requires the running of both pieces to work.
As to having a rom 2.3.6 based there really is no point we have fully functional roms that run beautiful with what we have not to mention that there's no real point in going back if we get a kexec or second boot working as further versions are going to be based off of a newer kernel and version of android.
Sent from my Nexus 7 using XDA Premium HD app
I'm now rooted thanks to this script by Lrs121! I strongly recommend those new to the process of root to use this script because it works!
Sent from my Milestone X2 using xda premium
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
DonInKansas said:
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
Click to expand...
Click to collapse
I'm glad it was able to help. I tried to make certain things more autonomous but unfortunately it does have to be specific, and handled as such. So there's not a lot of flexability in how the process is done by the user and by the script itself.
Sent from my Nexus 7
I've tested some superuser managing apps and so far the only one that works for our device is chainsdd's app. Clockworkmod's and chainfires supersu do not work well or at all. Please use the chainsdds app from the market or keep the one that the script installs as they work best.
Sent from my Milestone X2 using xda premium
A new script is coming soon. It will be an android to android script where you can root your phone using another phone or an android tablet. Thanks will go to the guys who have developed the p2p-abd tools. If the fast boot binarys are included
Sent from my Nexus 7 using XDA Premium HD app
Alpha for the arm aka android script is up. Testers are welcome to play with it. This is a very very basic build. Nothing is automatic, will be worked on as I go. The download, requirements and minor change log of what's included can be found on the second post. that post is now change log and unstable versions. Read what's included on the the log before trying. If you want to try but don't have and otg cable flash the preinstall img using a computer and play around with the arm adb binaries. Credit for the arm versions of the adb and fastboot binaries go to the original developers, they will be listed as I find the correct threads and sites I pulled them from are found.
Sent from my Nexus 7 using XDA Premium HD app
not working :|
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
zaq_37 said:
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
Click to expand...
Click to collapse
which pack did you use, each script is a little different
Lrs121 said:
which pack did you use, each script is a little different
Click to expand...
Click to collapse
Sorry I should have specified. It's the windows Pack.
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Lrs121 said:
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
zaq_37 said:
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
Click to expand...
Click to collapse
Hum I wonder what broke the windows script. Um really its up to you I can try to tear it apart and see if what's wrong but I'd need specific information from you in what's happening. But I'm a better Linux script writer so the Linux scripts are a bit more stable. Ubuntu 12.04 and up is best because the repositories have adb and fastboot included and can be installed. Both of which the script requires to run but any of the linux ones should work.
Sent from my SCH-I535 using XDA Premium 4 mobile app
On a side note I think I I figured out what's wrong. If I'm right correct me if I'm wrong, you tried to run the android-script.sh script from windows. If I'm wrong then I think the issue may be due to permissions
Sent from my SCH-I535 using XDA Premium 4 mobile app
Please help.
I recently received my Motorola Milestone X2 running 2.3.6. I have followed your method to a T. After the adb shell cmd, I receive no Superuser prompt. Then, after typing in the /preinstall/su cmd, it says: file not found, or file does not exist. I cannot remember. Can you help?
Thanks,
Jeremy

I made a script that roots and updates your watch to 5.0.1 in a click.

This version is Mac only sorry, will update for PC this week.
Directions:
1.) Download from https://www.dropbox.com/s/4zd9rz3akcr8zht/lollipop.zip?dl=0[1][1] to your desktop. (file size 124 mb), and extract it the zip.
2.) Open up terminal, and type navigate to the file via cd/Desktop/lollipop .That code only works if the extracted file is actually called lollipop and is in your desktop.
3.) Type sh runMe.sh into the terminal and just follow on screen instructions.
Short version of what it does: Used adb to unlock bootloader, Roots it, Copies over 5.0.1, Writes to cache, and reboots. Then optional install of TWRP recovery.
This code isn't specific to the G Watch, to make it work for your phone, just add two files...
Replace:
update.zip with your factory image of lolipop
LGGW-rootboot.img with temporary boot image for your device to give it root, can find this on forums like XDA TWRP (optional) custom recovery
Be sure to keep the file names the same, as that is what the script looks for! I'm too lazy now, but only 2 things need to be done to make it work for PC...
1.) Get the adb drivers and fastboot, and put it in the lollipop folder, make sure you keep the names the same as the ones in there now.
2.) On the script called runMe and called, everywhere it says ./fastboot or ./adb-mac, get rid of the ./ part, so it would just say fastboot or adbmac
works wirh 4.4W1?
solved, found ota to 4.4w.2
starbase64 said:
works wirh 4.4W1?
solved, found ota to 4.4w.2
Click to expand...
Click to collapse
Yea! It upgrades any version, be i t 4.4 or 4.4.1
Oh, the irony, using android devices on a mac . Can't wait for the windows version though, thanks for your work, man
This worked like a charm for me! I was up and running within 5 minutes -- with no previous ADB experience in my life. I recommend anyone with a mac available to use this if you want to avoid all of the manual work. Thanks again, pal.
Any progress on PC version?

[SCRIPT][UTILITY] Suicide Flash for Moto

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

Categories

Resources