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
Related
Important Update on Dec 2, 2011: Please do not update to Vizio Update 1.5. This will remove the root as well as disable this hack. According to user felixand in this Post.
I decided to start a new thread.
For those who would like to root, please see the instructions in the first post of this thread. This works for me.
http://forum.xda-developers.com/showthread.php?p=18805532
### Please use V3 version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip ###
Edited to add: If the above DooMLoRD method does not work you can use SuperOneClick. SuperOneClick can be found here: SuperOneClick. Download it and expand it. You will also need to download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip. Expand it as well. Copy the new zergRush binary from the files directory of DooMLord into the exploits directory of the SuperOneClick folder. Then run SuperOneClick to root. Thanks to those who tried this method. See post by marvin02 below.
ACKNOWLEDGEMENTS:
I am not the original developer. I just helped test it. Please thank the developer of zergRush who fixed this code on the Vizio. Post by Ch4lky here.
http://forum.xda-developers.com/showthread.php?p=19396835
For those interested in the original source code of this exploit it is here.
Source code: https://github.com/revolutionary/zergRush
Binary: https://github.com/revolutionary/zergRush/downloads
Edited: Info about Vizio update 1.5 on Dec 2, 2011.
so to read into what you are posting - we need to follow directions and use the http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
which is "DooMLoRD_v3_ROOT-zergRush-busybox-su.zip"
again, I am at work and can't download, but does above file contain the additional files called out in the script - namely busybox, su, and superuser.apk - if I were to guess from the filename, I would say yes...
to sum up:
place the 4 fileset(s) into a common directory under your adb setup - for consistency - we'll call this "files"
so we end up with
./files/zergRush
./files/busybox
./files/su
./files/Superuser.apk
is this about right?
Rich
Yes, that is correct.
okay - so the next step is the rewriting of the vold.fstab file to properly map the internal mount point and the external microSDHD card.
I remember seeing something on the Pandigital Novel forums that had suggestions on this topic...
Any ideas as to what the Vizio needs?
1) first so as not to break the current OS settings
2) then, to remap the mount point as needed so that software like APP2SD will behave correctly.
(looking forward to getting home tonight)
Rich
Wow, I was about ready to get rid of this thing. Will be giving this a go today and seeing about some dev support for roms and what not.
Kudos!
For me the doomlord script stuck waiting for the device.
I put the zergrush exploit into the exploits folder of SOC 2.2 (replace the one that is there) and it worked liked a charm.
Edit: SD Card mount point mod
If you are having issues rooting here is some troubleshooting:
To test your connection with adb:
After installing the drivers open a command prompt in the folder where the adb.exe is located at, make sure USB debugging is on and connect your VTAB to your computer.
Now type "adb devices" without the quotes and you should see:
D:\Android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your serial number here device
If this does not work then adb is not connecting to your VTAB.
For me the version of adb that is packaged with the doom script does not connect, but the version packaged with SOC 2.2 does. I copied the zergRush exploit from doom's script to the exploit folder on SOC 2.2 and used SOC. I am on WinXP Pro.
If you are using 64 bit windows make sure you install the drivers as an admin and run the doom script or SOC 2.2 as an admin.
Now...
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Maybe now that it has root, XDA should create a subforum for it?
blackcog said:
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Click to expand...
Click to collapse
This is great. Please post your progress. That will be very helpful.
majorpay said:
Maybe now that it has root, XDA should create a subforum for it?
Click to expand...
Click to collapse
We have to request it here.
http://forum.xda-developers.com/showthread.php?t=1301121
rprr said:
This is great. Please post your progress. That will be very helpful.
Click to expand...
Click to collapse
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
May I ask how you are trying to dump the boot img?
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
sigeltek said:
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
Click to expand...
Click to collapse
Thanks, I showed that to my DW and she burst out laughing But, the real credit should go to the devs of zergRush and Ch4lky in particular. Please see my OP for the link to Ch4lky's post if you wish to "Thank" his post.
Same problem here.
The doomlord rooting kit did not work for me either. However, the superoneclick 2.2 with zergrush exploit copied into the exploit folder did work.
---------- Post added at 09:13 PM ---------- Previous post was at 08:52 PM ----------
Do get my device rooted runnning ADB under Vista (32-bit) I did the following:
1) First the Vizio provided ADB driver would not install. I instead did the following.
2) After making sure that any previous drivers were uninstalled from Device Manager including the Android Composite ADB driver. This driver would install for my VTAB successully but I was unable to communicate to the tablet using ADB. I deleted this driver and clicked on "delete the driver software". I also deleted the USB mass storage device and USB composit device.
3) I did a clean boot of the VTAB and then enabled the USB debugging.
4) I connected the VTAB to the USB port and this enabled "installing new hardware"
5) On my machine, I allowed it to search for the device driver and the key was to ensure that it would fail and close.
6) Go into control panel, device manager and you should now have other device named VTAB1008 with yellow highlight.
7) Right mouse click and select "update driver software"
8) then select "browse my computer for driver software"
9) then select "let me pick from a list of device drivers"
10) Select "ADB interface" and then select "Android Sooner ADB testing interface".
11) Once this driver was installed, I was successful in seeing the VTAB through ADB.
12) Install SuperOneClick version 2.2
13) Download the doomlord V3 toolkit and copy the zergrush file under the /files directory to the exploit directory under SuperOneClick (replacing the existing zergrush file)
14) Once this was done, SuperOneClick was successful
rprr said:
May I ask how you are trying to dump the boot img?
Click to expand...
Click to collapse
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
blackcog said:
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
Click to expand...
Click to collapse
Sorry about your VTAB. May I ask again how you were trying to extract the boot.img?
marvin02 said:
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
Click to expand...
Click to collapse
Thanks. I did try that but still cannot get to the boot.img.
If you, like me, forgot to use RootKeeper before you upgraded to ICS you probably started to miss root soon after upgrade.
Luckily an exploit for Linux kernels version 2.6.39 - 3.2 have been released.
So I just packaged it with some nice scripts to install su.
Instructions:
(Windows Only)
Install USB drivers http://www.motorola.com/consumers/v/index.jsp?vgnextoid=0351f6a559431210VgnVCM1000008406b00aRCRD
(All)
1. Extract the zipfile
2. Enable USB debugging
3. Run the appropriate script file
4. Install superuser from market.
Credits to Saurik who ported the exploit to Android and also for finding the correct hex values for this ROM.
Credits to Max Lee and DooMLoRD from witch I took their previous root packages and modified it.
Windows and Mac scripts are untested so please report their workingness
Very nice! Been waiting for exactly this. Thanks!
many thanks !!! I installed ICS and rolled back to 2.3.6 beacause can't root and have many soft with root
I will re upgrade to the ISC one again and test your package
Not really sure if I do this correctly.
First I unzip the files; then debug on; connect phone to the pc; and finally run the "run-windows" file? Well it doesn't work...
This for Verizon? Cdma?
Sent from my DROID RAZR using XDA App
pajn said:
If you, like me, forgot to use RootKeeper before you upgraded to ICS you probably started to miss root soon after upgrade.
Luckily an exploit for Linux kernels version 2.6.39 - 3.2 have been released.
So I just packaged it with some nice scripts to install su.
If you are on Windows you will have to install USB drivers but for us who are not
it's simply to enable USB debugging and run the appropriate script.
After that you probably want to install superuser from market.
Credits to Saurik who ported the exploit to Android and also for finding the correct hex values for this ROM.
Credits to Max Lee and DooMLoRD from witch I took their previous root packages and modified it.
Windows and Mac scripts are untested so please report their workingness
Click to expand...
Click to collapse
Thanks man!
twistmycap said:
This for Verizon? Cdma?
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
There is no ICS for CDMA version atm... So obviously... You cannot root something that does not exist..
drinkluder1 said:
Not really sure if I do this correctly.
First I unzip the files; then debug on; connect phone to the pc; and finally run the "run-windows" file? Well it doesn't work...
Click to expand...
Click to collapse
I missed two DLL files for windows, but have now uploaded a fixed version.
Also make sure that you have the USB drivers installed and that you manually install superuser from market (this is so you can get updates, if I included the apk in the packages it would stick to that version)
I wrote some better instructions to hopefully easier it a bit.
EDIT:
For CDMA, it would work if you guys would get the rom to. Well theoretically Motorola could patch the exploit before releasing a CDMA version but I find that unlikely.
I'm surprised by the quick finish
but now my phone are Rooted
THANKS !
Blah lol
Sent from my DROID RAZR using XDA App
pajn said:
I missed two DLL files for windows, but have now uploaded a fixed version.
Click to expand...
Click to collapse
Excellent, countryman! My ICS-device now rooted!
Wow, awesome! Been waiting for exactly this.
Now i'm gonna be waiting for my RAZR ICS.
Thanks very much!
pajn said:
If you, like me, forgot to use RootKeeper before you upgraded to ICS you probably started to miss root soon after upgrade.
3. Run the appropriate script file
Click to expand...
Click to collapse
Hahahaha, LoL.... It went like it cannot wait to show me anything.. And I did wonder first it was failing without checking... But, it was rooted, LoL... Amazing, really appreciate... I hopefully have waited for the day and never thought so soon... Well Done....
thank, worked for me.
but only if i didn't root the 651.73.30 and 651.167.20 before.
when i rooted before the update to ics, i got root permissions via shell but apps like titanium backup couldn't get root permissions.
devil696969 said:
when i rooted before the update to ics, i got root permissions via shell but apps like titanium backup couldn't get root permissions.
Click to expand...
Click to collapse
Thats because this only installs the su binary. You have to get the superuser app from market yourself.
pajn said:
Thats because this only installs the su binary. You have to get the superuser app from market yourself.
Click to expand...
Click to collapse
i did that. also assured that binary and app are the latest versions.
windows script not working
Worked perfect for me, thanks
Sent from my XT910 ICS using xda premium
Modified the script slightly to make it easier
Roots and then installs SU and Recovery
Do Not ROOT any of the Gingerbread OTA's
Windows Only
Download
MB159 said:
windows script not working
Click to expand...
Click to collapse
Seems to work fine for others.
Have you made sure you have USB drivers installed and that USB debbuging is enabled?
I was enjoying the beauty of having a rooted device, but now that I have received an update from Motorola (which I thought was ICS) I have lost root access.
I have a Photon 4g running 2.3.5, and I did my root using a OCR when I was on 2.3.4. I have tried that OCR again among others and torpedo photon and no luck. Every app I try says that it was denied superuser access (which is still installed). The only exception to this is Play Movies, which says that "This app currently does not support root access, and your device is rooted" I do not know where else to turn. I just want to be part of the cool kids again. Please someone help me.
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Shad0wguy said:
I have had success with the photon torpedo method on 2.3.5. I recommend trying it again being extra careful to follow the steps exactly.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
I used Motorola DROID 3 one click. Worked great.
Sent from my MB855 using XDA
Thank you, I will try the Droid 3 OCR, and if that does not work, see if I can get Torpedo to work, and if that does not work I will send it in to Motorola.
Use torpedo thru terminal emulator on your phone as I did
Sent from my Motorola Electrify using XDA
What worked for me was to use the command prompt on windows 7 instead of terminal emulator. For some reason, TE could not see the photon-torpedo file in the phone after i had transferred it there. Command prompt did.
Sent from my MB855 using xda premium
Also remember to reboot after!
I got the OTA update to 2.3.5 yesterday, and photon-torpedo is NOT working for me. After running photon-torpedo.sh, I get the error message, but my prompt doesn't change to # or root. Trying to run install-su.sh doesn't work since I'm not root and gives me permissions errors. Has anybody gotten photon-torpedo to work after yesterday's OTA update?
UPDATE:
I figured out the issue and a fix:
http://forum.xda-developers.com/showpost.php?p=28669160&postcount=363
JohnH4 said:
Photon torpedo was what worked for me, except that I had to push it from the command prompt on my windows 7 laptop. For some reason, I couldn't get it to work with Terminal emulator. Good luck!
Click to expand...
Click to collapse
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
can someone please help me with my post above?
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
here's an easy way to do Photon Torpedo: http://www.groovypost.com/howto/motorola-photon-4-g-how-to-root-your-phone/
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
You don't need to create /data/tmp in your phone's internal storage. That folder already exists inside the system partitions. Use ADB to push it in. Follow the instructions in the Photon Torpedo thread.
Sent from my MB855 using xda app-developers app
I didn't have my phone Rooted before the update to Android 2.3.5 but after trying several different methods I found one that worked with ADB and torpedo program/files with a step by step that actually says to have 2.3.5 I followed the instructions and it worked for me, only problem I had was I unzipped the photon-torpedo.tar file by mistake... it doesn't have to be unzipped into the folder just place the whole file in the folder.
Hears a link to the walk through from gamerguy13
instructables.com/id/How-to-get-root-access-on-your-Motorola-PhotonEle/?ALLSTEPS
Good luck everyone else trying to root or re-root.
DiamondJay20 said:
what commands do I have to enter to get my Windows 7 CP to do things on the Photon? Also, I tried making a data folder in my internal storage, then a tmp, and put the winrar photon torpedo into it and tried following the steps and it didn't work. I'm on 2.3.5 too. What could I be doing wrong?
Click to expand...
Click to collapse
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
I would think twice before taking that ota update. Currently, under 2.34, your bootloader should be unlockable. The main effect of the 2.35 update is to lock the bootloader.
Sent from my MB855 using xda premium
Worked for me
JohnH4 said:
The MoPho I rooted is fairly unique, so I can't promise anything, but this is what worked for me. All credit goes to edgan. I didn't develop anything.
Photon Root Instructions
1. Create a folder in the C:/ drive on your Windows 7 machine called Photon root. (You can call it anything you want, but that’s what I called mine and will use for the purpose of this post).
2. Download and install the adb package from here and install them into C:/Photon root.
3. Download photon-torpedo.tar from here and copy it to C:/Photon root in your windows machine. Do not unzip it.
4. On your phone, go to Settings > Applications > Development and select USB Debugging.
5. Plug your phone to your computer and on your phone, set it to USB Mass Storage.
6. Copy photon-torpedo.tar from C:/Photon Root to your phone’s internal storage using Windows 7. Don’t put it in any folder, and leave it zipped.
7. Install Superuser from the Market. (This is absolutely necessary to do before you get started or it won’t work)
8. Open the command prompt (Start >> run “cmd” >> enter)
9. Type the following commands – don’t worry about the errors, it will be all right
• cd C:/photon root
• adb push photon-torpedo.tar /data/tmp
• adb shell
• cd /data/tmp
• /bin/tar xf /data/tmp/photon-torpedo.tar
• /data/tmp/photon-torpedo.sh
• /data/tmp/install-su.sh
10. That's it. Reboot and enjoy.
Click to expand...
Click to collapse
John was right, just ignore the errors. This method by edgan worked for me.
---------- Post added at 07:28 PM ---------- Previous post was at 07:16 PM ----------
bitbang3r said:
For those who successfully rooted w/Photon Torpedo... is your 2.3.5 from the May Soak, was it re-soaked last week, or was it 2.3.5'ed for the first time this week?
God, I'm glad I told Moto to fsck off & swore I'd never install another Moto update (soak, push, or otherwise) again. Refusing last week's soak just might have enabled me to grudgingly endure my final 50 days with this miserable excuse for an Android phone.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
I agree with bitbang, I've had enough of this bullsh*t from Motorola. It's time for me to shop around. Unfortunately for me, I have a little more than a year on my contract! I've heard that Sprint had some kind of buy back or release program where they let you trade in your phone for something new (for a "small" fee, of course). It just might be worth it to get away from Moto. This smartphone technology changes way too fast for 2 year contracts anyway.
It's a shame. When I can get this phone to work properly, it is awesome, I'm sure bitbang even agrees with that but it is definately time to move on. The Samsung Galaxy 3 looks pretty cool!
amlodipine said:
Hey Mopho's - I'm currently running a rooted (via shabby's AIO) stock sprint v 2.3.4 .... System Version : (45.3.6.MB855.Sprint.en.US) / Build number : 4.5.1A-1_SUN-198_6
I've tried downloading the OTA 2.3.5 via wifi, and installation was going ... but upon reboot - it says update failed. Tried this 2x - I didn't see many commenting on going back to an original stock rom before, getting the OTA update, and that rather - rooted devices would be unrooted after 2.3.5 OTA. I've never installed any other ROM besides what came with the phone...
Was there something I needed to do to "unroot" or revert without wiping/losing my current settings / apps ? Basically, what can I do to get this done
rooted apps installed : AdAway / Superuser free / Root Basic Check free / LBE Privacy Guard / Wifitether
Thanks in advance for the info. I realize Shabby's AIO will not re-root my phone, so will need to see the ADB/Torpedo methods posted here after. I just need to get the OTA update working first.
Click to expand...
Click to collapse
When the update fails and you see the Android guy with the "!", press and hold both volume up and down. This will show you on the screen why it failed. Common causes for failure are mods to the build.prop file or removal of core apps.
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
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...