I see random postings from others that also have the Motorola Electrify and was hoping to start a thread where Electrify owners could post a little information as to those things already developed for the Photon that work (or do not work) for our sister phone. Personally, I was a little apprehensive about diving in and applying mods haphazardly without some other brave soul taking the leap first.
I can confirm that the AIO root method by shabbypenguin (LINK) works on the Electrify and I would have commented in that thread, but my noobness on this site did not allow me to do so in the dev topics. I actually saw another Electrify owner's post confirming this, not on xda, but rather in comments on the youtube AIO root Video Instructions (thanks qbking77).
I had previously tried the root with dock method by edgan, but was unsuccessful.
My hope is that mods will allow this post to continue and that other Electrify users might find it useful and likewise contribute.
Thanks
note: I have started to add some links in post #3 below to some Electrify-specific information.
I thought I would mention that my local US Cellular has promotional pricing (-25%) on the HD Dock and Vehicle Navigation Dock for the Electrify which retail for $100 and $60 respectively. I have no idea if these are compatible with those made for the Photon, or vice versa.
Here is some basic info from the About Phone screen for the Motorola Electrify:
Motorola Electrify model MB853
Stock System version 45.1.167.MB853.USC.en.US
Android Version 2.3.4
Baseband Version n_01.10.00s.xj
Webtop Version WT-1.2.0-131-4
Kernel Version 2.6.32.9-00010-ge26b22b
[email protected]#2
Build number 4.5.1A_SUN_USC_16.7
PRL Version 15112
---------------------------
LINKS:
Link to Motorola Electrify kernel.img: HERE
Link to Stock (USC) Motorola Electrify System Dump (not cwm flashable)
and Deodexed version (cwm flashable - by shabbypenguin) in dev forums.HERE
Team US Cellular Electrify Forum - for confirmation of working mods, many originally posted on XDA.
Stock Motorola Electrify SBF File - for unrooting and re-locking bootloader
Motorola Owner's Forum for ELECTRIFY
Motorola Product Support page for ELECTRIFY
Motorola Media Link for Windows
ZumoCast for Windows by Motorola
If there is other information that might assist devs in determining compatibility for projects already developed or in development, please advise (but please be specific, as I take my noobivity seriously).
try flashing cwm, i would imagine youll be fine from that. but the big test will be if my kernel works/boots yall's phone
A full system dump would be great...
Requirements:
- Rooted Electrify
- Android SDK
Instructions:
- Connect via adb and issue the following commands:
Code:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
- Upload systemdump.tgz to a file sharing host like MultiUpload, Filesonic, etc. and post the link here.
Thanks!
actually a better way to do it would just use dd so i could get stock kernel and see if there is any if at all differences.
Question...is 4G Wimax and on Sprints /Clears wimax network?...im just hoping this phone and the photon in japan on kdd may give some hints or help with fixing the broke wimax when unlocked and also gsm radio rom that will work in the us
Sent from my MB855 using XDA App
Well, now I understand why I'm over here posting in the "General" section and not the development threads
I've spent the last several hours reading and installing the SDK only to discover I can't even figure out how to get it configured properly. I will succeed, but I'm too tired right now to continue and have other things to do later today. I'll try to provide more information as soon as I can get back to it.
And thanks Beach_Head and shabbypenguin for your interest and assistance.
just cheat, in the AIO root there is adb.exe and two dll files, toss them in your user's folder ( C:/Users/yourusernamehere) then you can just hit teh windows key and r. type in cmd hit enter, and you will be in command prompt in a directory with adb available (no sdk installing needed )
Beach_Head said:
A full system dump would be great...
Requirements:
- Rooted Electrify
- Android SDK
Instructions:
- Connect via adb and issue the following commands:
Code:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
- Upload systemdump.tgz to a file sharing host like MultiUpload, Filesonic, etc. and post the link here.
Thanks!
Click to expand...
Click to collapse
I get an error using the "busybox tar czvf" entry:
tar: invalid option --z
BusyBox v1.18.0.git multicell binary
??
I'll be away from the computer the rest of the day till late. Thanks again for the help. BTW, following shabbypenguin's adb "cheat" and got command window, but did not realize I needed to open superuser on the device to accept permissions (kept getting denied - duh)
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/eletricfykernel.img
upload that for me please
you can then use dd to copy the rest of the phone
It looks like your BusyBox build doesn't include gzip. Where'd you get it from?
Anyway, download Busybox by Stericson from Market and install a newer BusyBox build.
That command will work guaranteed...
Thanks!
drenner99 said:
I get an error using the "busybox tar czvf" entry:
tar: invalid option --z
BusyBox v1.18.0.git multicell binary
??
I'll be away from the computer the rest of the day till late. Thanks again for the help. BTW, following shappypenguin's adb "cheat" and got command window, but did not realize I needed to open superuser on the device to accept permissions (kept getting denied - duh)
Click to expand...
Click to collapse
drenner99 said:
Well, now I understand why I'm over here posting in the "General" section and not the development threads
I've spent the last several hours reading and installing the SDK only to discover I can't even figure out how to get it configured properly. I will succeed, but I'm too tired right now to continue and have other things to do later today. I'll try to provide more information as soon as I can get back to it.
And thanks Beach_Head and shabbypenguin for your interest and assistance.
Click to expand...
Click to collapse
You have been a positive contributor, and so I proudly give you your first "Thanks."
shabbypenguin said:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/eletricfykernel.img
upload that for me please
you can then use dd to copy the rest of the phone
Click to expand...
Click to collapse
Here is the file you requested from the Electrify (electrifykernel.zip)
hopefully it contains what we're looking for....
Beach_Head said:
It looks like your BusyBox build doesn't include gzip. Where'd you get it from?
Anyway, download Busybox by Stericson from Market and install a newer BusyBox build.
That command will work guaranteed...
Thanks!
Click to expand...
Click to collapse
@Beach_Head, Thanks again. I did as you suggested and installed the newer busybox (1.19.2), but I still get the invalid option ("z") error when I enter the command
"busybox tar czvf /sdcard/systemdump.tgz /system"
from your code, and am then presented with a list of valid options, "z" not being one of them. Are we sure the czvf part of that line is as you intended? I'm still willing to give it a go if it will produce info that is helpful (see post immediately above with kernel.img file).
Thanks once again.
deedscreen said:
You have been a positive contributor, and so I proudly give you your first "Thanks."
Click to expand...
Click to collapse
I am truly humbled and can only say, you're welcome!
Yes. The z switch is for gzip...
Anyway, can you try without the z swicth.
So: busybox tar cvf /sdcard/systemdump.tgz /system
And then just zip it up again via WinRar or 7Zip before you upload it here...
Thanks!
drenner99 said:
@Beach_Head, Thanks again. I did as you suggested and installed the newer busybox (1.19.2), but I still get the invalid option ("z") error when I enter the command
"busybox tar czvf /sdcard/systemdump.tgz /system"
from your code, and am then presented with a list of valid options, "z" not being one of them. Are we sure the czvf part of that line is as you intended? I'm still willing to give it a go if it will produce info that is helpful (see post immediately above with kernel.img file).
Thanks once again.
Click to expand...
Click to collapse
I'm a moto electrify rooted and bootloader unlocked user.
Everything seems to work (as far as the root/unlock), but shabby's kernals are somewhat unstable on the electrify. Broken wi-fi is my only concern, and even with the wi-fi fix we haven't been able to run it.
one of my issues - now this isn't specifically about shabby's kernal or anything like that, but more of setcpu. Setcpu doesn't give me the option to scale, unfortunately.
my kernels are unstable on the photon so thats nothing new
what wifi fix? wifi is busted in rc2 due to modules needing to be updated. they arent part of the kernel they are instead loaded by the rom but they need to have the config file from the kernel in order to make them properly and thats where its all failing
shabbypenguin said:
my kernels are unstable on the photon so thats nothing new
what wifi fix? wifi is busted in rc2 due to modules needing to be updated. they arent part of the kernel they are instead loaded by the rom but they need to have the config file from the kernel in order to make them properly and thats where its all failing
Click to expand...
Click to collapse
Is there anything I can get you to fix the wifi in rc 2?
Related
Hello everyone!
You may or may not know me, however I have secretly been working behind the scenes with ChiefzReloaded to learn how Android works. Together we have been trying to develop new ways to root the Slide, primarily because we both landed in a sticky situation that left us both without root and without a way to revert to root.
After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
To get started, please see the bottom of this post for the link and download it. You will want to download it to your computer and not your phone's SD card. Also, you will need the tools from the Android SDK. I would suggest extracting the file from my zip at the bottom of this page into the Android SDK's tools directory.
Extract the zip
Make sure your phone is in USB debugging mode AND you are in "Charge Only" mode.
Connect your phone to your computer.
Make sure you're in the same directory as where exploid is extracted before continuing to the next step.
Issue the following command: adb push exploid /sqlite_stmt_journals. Note: It MUST be in that directory - NO exceptions.
Run: adb shell
Run: cd /sqlite_stmt_journals
Run: chmod 0755 exploid
Run: ./exploid
Toggle your phone's Wifi (on or off, however you wish to do that).
Now (again) run: ./exploid (if prompted for a password enter: secretlol)
The next line should now begin with a pound (#) - if not, then something isn't setup right. Make sure to follow the directions verbatim. If you suspect you did follow them correctly, please reply to this post letting me know.
You should now be root! At this point you can do many things, but if you're looking to flash a custom ROM, continue to these instructions:
[NEW 10/18/2010:]
Steps 1-12 are intended to get you the ability to flash mtd0.img (which previously required using the SimpleRoot method) by gaining root inside of Android. By following the instructions in the rest of this section, it will allow you to flash a ROM or S-OFF your device:
The files you need are at: http://forum.xda-developers.com/showthread.php?t=703076- download both files linked in there (ESPRIMG.zip and SlideEng-package.zip)
Extract the contents of SlideEng-package.zip to a place of your choosing on your computer.
Place the entire (unextracted) ESPRIMG.zip on your SDcard.
Now push the files 'flash_image' and 'mtd0.img' that you just extracted from SlideEng-package.zip to /data/local using 'adb push'. (Noob? Instead of using 'adb push', install Droid Explorer and, using that utility, copy the 'flash_image' and 'mtd0.img' files to /data/local on your Slide)
Now I'm going to assume your phone is at root prompt (#) using steps 1-12. So now do (without typing the '#' symbols in front of both lines - they're just there to remind you that you need to be at a '#' prompt):
Code:
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Before you reboot make sure that the ESPRIMG.zip is on your SDcard!
Now turn off the phone.
Then press Volume-Down + Power.
The phone will power on and after about 5 minutes of verifying ESPRIMG.zip it will ask you if you want to flash it.
Press Volume-Up for 'YES' and wait until it finishes (ABSOLUTELY DO NOT POWER DOWN WHILE IT'S STILL FLASHING!!!).
Now when you go into recovery it should allow you to 'Apply update.zip from sdcard' (booting into Clockwork). If you don't have the Clockwork update.zip, here it is: http://www.4shared.com/file/OTRU7T3y/update_2.html (rename to update.zip after downloading since it's currently update_2.zip, then place it on your sdcard).
[/NEW 10/18/2010]
[NEW 12/30/2010]
Optional: Now that you're rooted you might want to disable all flash memory protections so you can permanently flash Clockworkmod (recovery - no more using an update.zip!) as well as other random things. Check here for details: http://forum.xda-developers.com/showthread.php?t=798168
[/NEW 12/30/2010]
CREDIT GOES TO:
[*] ChiefzReloaded! (For helping me learn the intricacies of Android and patiently answering all of my questions)
[*] 743C (For developing the original exploit)
Source code: (Yes, it's hackish. I was just trying to figure out why the system kept rebooting and haven't cleaned up the code since) download
DOWNLOAD:
http://www.4shared.com/file/CZsxSq-f/exploid.html
DONATE:
(Anything helps!)
(Some people may wonder why this is special compared to the One Click Root application. What's important is that One Click Root doesn't work on Slides running production/retail software, likely the same problem I had to fix to get exploid to work in my version.)
Thats whats up!!
If you be trollin then YOU BES TRAWLLIN
But if not then good job nb!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
Sure, I was getting around to that - and I understand your concern. I'll post it in a second.
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Sent from my T-Mobile myTouch 3G Slide using XDA App
r0man said:
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Click to expand...
Click to collapse
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
nbetcher said:
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Click to expand...
Click to collapse
Ill take a look at it when I get home.
ilostchild said:
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
Click to expand...
Click to collapse
I actually had to do a lot of work on it. It doesn't quite work the same as the original exploid simply because the original exploid crashes the entire system and reboots. This causes the rootshell to never be committed to NAND and thus you get no where. I had to keep playing with things until I found a different method that works. It took several hours of me being upset with it, but watched the latest Burn Notice, came back to it, and BAM I had a stroke of genius.
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Armyjon88 said:
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Click to expand...
Click to collapse
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Sweet
Sent from my T-Mobile myTouch 3G Slide using XDA App
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
statuzz said:
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
Click to expand...
Click to collapse
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
nbetcher said:
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Click to expand...
Click to collapse
Let me know if you want to work together on some kind of one-click root app for the Slide. If the commands work through the terminal on the phone itself rather than via adb, I could probably make this into an app already, but since you're working on a more non-developer-friendly version, I'll just wait until that's out
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
I'm delaying the release of my non-developer program for another couple hours.
As far as what you said above, all you need to do after gaining the # prompt is (in a separate window):
adb push flash_image /data/local
adb push mtd0.img /data/local
(switch back to your # adb shell, then type
cd /data/local
chmod 04755 flash_image
./flash_image misc mtd0.img
Then reboot and apply the ESPRIMG.zip. All of these files are found on the same post that I referenced in my OP. These instructions are all in that same page.
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
Im also stuck since im not sure if you can update to eng from the ota..But first i want to personally thank the OP & CR for providing this.
This would be great for a One Click method
this would be nice to work into a one click root!
And This did work for me!
Does this root method gets /system moumted when android running?In short do we finaly get metamorph and root explorer working?
Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_ERIS.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!
also need...
adb shell ls -l -R /sys/devices/platform > platform_structure_ERIS.txt
and
adb shell ls -l -R /sys/devices/virtual > virtual_structure_ERIS.txt
If you guys don't mind taking a moment
I would love to help but I'm not stock do you have an Eris? It is possible to convert back to stock w/no root I believe.
Sent from my Eris Lightning 3.02
settlethestorm said:
I would love to help but I'm not stock do you have an Eris? It is possible to convert back to stock w/no root I believe.
Sent from my Eris Lightning 3.02
Click to expand...
Click to collapse
I'm afraid I do not have an Eris That's why I'm hoping to get some help from the community
Tried but would not output a file
dragon1018 said:
Tried but would not output a file
Click to expand...
Click to collapse
What did it output?
Doward said:
What did it output?
Click to expand...
Click to collapse
Please say ice cream please say ice cream pls say ice cream
file not found
dragon1018 said:
file not found
Click to expand...
Click to collapse
Ok, let's start simple then.
Try this:
Run "adb shell" (minus the quotes)
At the new prompt, just type "ls" (again, no quotes) and see what you get.
If you get a directory listing, continue - if you get an error, post the error here.
If you DO get a directory listing, try this -
cd /sys/devices
and see if that gives you an error...
Got it to work and push out the text files. I did not realize when you posted this was that your looking for a stock eris. I have a nan backup of the stock eris prior to installing roms. Obviously I already have root access at this point so I dont know if that is gonna help. Let me know Ill keep the files on hand
dragon1018 said:
Got it to work and push out the text files. I did not realize when you posted this was that your looking for a stock eris. I have a nan backup of the stock eris prior to installing roms. Obviously I already have root access at this point so I dont know if that is gonna help. Let me know Ill keep the files on hand
Click to expand...
Click to collapse
I definitely prefer non-rooted, if it's not too much trouble
[Edit]
Sorry, what I wrote earlier won't do you a bit of good, you need someone with a rooted live phone, since /sys is created on the fly by the booted kernel. (I missed that by reading too quickly).
I might be able to get to it, but it will take a little bit of time.
bftb0
Here you go (attached).
For what it is worth, here's some details on the state of the phone this was extracted from:
- Cupcake MR2 (1.17.605.1) PB00IMG.ZIP components (boot, recovery, system, data, radio) flashed & booted
- OTA2.1 (pre-July OTA) accepted
- after OTA2.1 completed & booted, OTA2.1+ (July 17 OTA) accepted and run
- after completetion of 7/17 OTA install, boot up (no Google account setup) & perform Factory Reset
- boot after FR; no activation and no Google account setup.
- shutdown. Install Amon_RA recovery via S-OFF bootloader and fastboot
- boot Amon_RA; make Nandroid Backup.
(The preceding steps took place 7/17/2010)
Tonight, I restored the 7/17 "clean" 7/17 OTA2.1+ Nandroid backup, and then:
- overflashed engtools3.zip
(This is a minimal root kit containing only "su", "SuperUser.apk", and "flash_image"; the latter is not used)
Then, your files were generated via an ADB shell promoted to root via "su".
In passing, I note that the HTC toolbox version of "ls", when invoked as 'ls -l -R' does not list major,minor device numbers for special device files - is that needed?
Baseband version: 2.42.01.04.27
Kernel version: 2.6.29-8a03cb9a [email protected] #1
Build number: 2.37.605.4 CL185970 release-keys
Software number: 2.37.605.4
PRI Version: 2.11_002
PRL Version: 51919
Just out of curiosity - what's this needed for?
bftb0
Long story short, I'm collecting as much underlying (Linux, not so much Android) hardware information as I can, so that I can compile a list of what phones have what hardware available for direct hardware access.
I've noticed in my short stint of Android programming, that a LOT of hardware features are left on the table in individual phones. I'd like to get some of those back
[GUIDE] Fre3vo / Fre3dom Official Thread (Discontinued)
#teamwin is proud to announce the Fre3vo tool for the HTC EVO 3D and Sensation!
What is Fre3vo: Fre3vo is a temp-root acquiring tool, allowing users access to a root shell on their HTC EVO 3D and Sensation devices.
What is Fre3dom: Fre3dom was the name of the tool being developed to enable S-OFF on the EVO 3D and Sensation. This has been abandon since AlphaRevX has announced on twitter that they've had the devices open for weeks now.
Fre3vo can be downloaded here: http://tinyw.in/1lJ
Prereqs:
1. You must be able to push files via adb to your device.
2. You must know what a shell is.
Instructions:
1. Download the fre3vo zip
2. Unzip the fre3vo binary
3. Push the binary via 'adb push fre3vo /data/local/tmp'
4. Change the permissions via 'adb shell chmod 777 /data/local/tmp/fre3vo'
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt. (Some may get more messages, but it seems the Sensation buffers the stderr more than the EVO 3D)
run 'adb shell' and you should have a '#' prompt instead of '%'.
This is temporary root. A reboot will clobber it. There are many threads with scripts for doing what the community has dubbed "perma-temp root", which lets you run all your root-based apps.
[Reserved for future details]
[More reserved for future use]
Want to thank you and your team for all the effort and contributions you've given to this community.
I have updated the FAQ with the contents of last nights "meeting".
I will update this post with results once testing beings.
Thanks Again!
adb?
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
http://pastebin.com/wiQc8Mid
steal25 said:
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
Click to expand...
Click to collapse
Here's a good thread regarding ADB. Sorry if you already know all that. I've gotten it to work, but every command results in the "adb server is out of date. killing......" message. In the end, the command goes through, but it has to restart the sever every single time.
FWIW, I didn't take any updates.
This thread is closed. When this rom is ready to go, then it can be re-opened, until then I don't see any actual development ongoing in here.
agrabren - PM me when your ready to post the rom.
Thread has been re-opened, sorry for the delay I am out of town
its all about getting su to stick
Rooting information added to the first thread. Please keep this thread on topic and without trolling, flaming. Any flaming or trolling may warrant a ban as we do not tolerate such things here at XDA.
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
yeah it does
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
Double confirm from me.
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
rooted here.. all updates applied.. confirmed..
Will we learn how the exploit was achieved, possibly post-perm-root?
installed it successfully but for some reason when i run su in terminal it does not give me root, and none of my root apps do not work am i doing something wrong or am i not understanding something?
Doward said:
Will we learn how the exploit was achieved, possibly post-perm-root?
Click to expand...
Click to collapse
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Thank you this worked for me on latest OTA.
DWhite456 said:
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Click to expand...
Click to collapse
#teamwin only tells HTC about intentional exploits. non intentional they dont:
20:28 <@joshua_> agrabren, By the way, traditionally, unrevoked's policy is to report to vendors holes that appear to be 'intentional' (see skyagent), but to package and protect vulnerabilities like that the best we can.
20:29 <@agrabren> This was a non-intentional hole.
20:29 <@joshua_> Yeah. Traditionally, unrevoked just packs and protects that sort of thing until someone finally reverses them.
20:30 <@joshua_> We'd love to be able to do the responsible disclosure thing, but this is an arms race...
20:30 <@zule> htc created the arms race, we just fight fair
How do I update my path environment variable?
NEver mind found it here. Have to copy contents of 'Platform tools" to 'tools' folder.
https://sites.google.com/site/mophocorner/
Site to help with everything Motorola Photon 4G.
Hoping to help with newbies that want to flash, root, unlock, etc. before they get stuck and have to wait for replies to fix there phone, Hopefully this guide will just work and they wont HAVE to post for help. That is the point of this at least! Let me know if there is anything I can add or change and I will gladly give it some thought!
Thanks!
I have updated the page, just so everyone knows!! Check it out!!! Let me know if I am missing anything.
Sent from my Xoom using XDA
The photon torpedo method is needed to root the 2.3.5 version just released.
Sent from my MB855 using Tapatalk 2
THANKS!
Thank you for that. Added the Torpedo root method! =]
Thanks for putting all that info into one spot! Definitely helps out that much more as it is somewhat easier to refer to rather than bouncing from one post to another here in the forums! I would imagine it'll help out many people (including me!).
I'm still fairly new to some things and some times the added explanation of certain topics and/or issues is what's needed to get the job done!
Also, as far as the *photon-torpedo* root method goes... I used that method without an issue on Android 2.3.4. After updating to Android 2.3.5 the other day, I used that same method again without issue and it worked perfectly! Unfortunately (at least from what I've read), being that I updated to 2.3.5, I won't be able to unlock the bootloader as if right now. Not really something I'm too concerned about, being that I hadn't prior to the update anyway.
Sent from my MB855 using Tapatalk 2
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Grep,
To answer your question, yes. The new update unroots your device so you will have to re-root using the photon-torpedo method again.
I was rooted prior to the update with that method and after the update I was un-rooted! Trying to re-root using Terminal Emulator on device wouldn't work. Got "permissions denied" when running the tar command. But, using adb on the computer worked without a problem!
So basically, just redo the torpedo root method from step 1 and you'll successfully get root back guaranteed!!
Hope that helps!
Also, I had the SU binary in place as you did along with other root specific apps. Those apps are pretty much worthless until you gain root again.
It has been confirmed in the "soak" that 2.3.5 update will completely un-root your device...
Sent from my MB855 using Tapatalk 2
nice. should come in handy for others. even me cuz im kind of a noob.... waiting for way around locked bootloader after 2.3.5 ota
Sent from my Motorola Electrify using XDA
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Sent from my MB855 using Tapatalk 2
Root
You could always use root-keeper from the market if your lazy like me.
the link to the download torpedo is not working
spursrob said:
the link to the download torpedo is not working
Click to expand...
Click to collapse
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Lokifish Marz said:
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Click to expand...
Click to collapse
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
cool old lady said:
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
Click to expand...
Click to collapse
try it now, post 6. Are you on 2.3.4 or 2.3.5? If you're on 2.3.4 then just use the root/unlock/relock pack (the link is at the top of post 6.
OK - I see it now and I've downloaded it - thank you very much. I am on 2.3.5 from the soak test.
Are these still the correct/only instructions? If so I may still be in trouble...my "favorite method....into /data/tmp"? I don't know any method, much less have a favorite.
Instructions:
Use your favorite method to get photon-torpedo.tar into /data/tmp
Install Superuser from the Market
Install Android Terminal Emulator from the Market
Run Android Terminal Emulator
Run cd /data/tmp
Run /bin/tar xf /data/tmp/photon-torpedo.tar
Run /data/tmp/photon-torpedo.sh
Run /data/tmp/install-su.sh
I'm actually on my way to bed. I will write a more detailed walkthrough tomorrow and post it in the Photon Compendium. Eventually I plan to script the entire process but am working on unified webtop stuff right now.
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Me to, had to used one click Root (20 times)
Navigate to the Android Market and install the “Superuser” application from ChainsDD
Download and extract 22MB Root-Unlock-Relock.zip from the Imperium website
Go to the "rsd drivers" folder located in the Root-Unlock-Relock folder and install the drivers for your system (32bit or 64bit windows)
Download photon-torpedo.tar
Place photon-torpedo.tar in the "AIO Root" folder located in the Root-Unlock-Relock folder
On your phone, in menu/settings/applications/development make sure usb debugging is checked
Connect your phone to your computer and select "charging" mode from the connections options in notifcations
From the "AIO Root" folder, double click the "Command Prompt" shortcut
Type the following commands:
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
Ignore the errors when running torpedo and let the process complete.
Once I get some free time I'll write a single script covering everything from rooting to SBFing back to stock. My goal is to get any given process down to ten keystrokes or less.
Hmph. Well....I think it worked. Root Checker says "congrats" - but wasn't it supposed to wipe all my stuff from the phone or something?
no root doesn't wipe data. (neither does unlock if done right)
Sent from my mopho
So I read around for rooting a x2 on linux and they all link back to rootzwiki article. ( Cant post the link cause im under 10 posts ) Well the link to mediafire is broken in the article for the download and was wondering if anyone knows where else to download this file or a different way to root on linux?
Thanks
tatumjef said:
So I read around for rooting a x2 on linux and they all link back to rootzwiki article. ( Cant post the link cause im under 10 posts ) Well the link to mediafire is broken in the article for the download and was wondering if anyone knows where else to download this file or a different way to root on linux?
Thanks
Click to expand...
Click to collapse
By the way this belongs in the questions section. as to your problem which x2 do you have the Droid x2 aka DX2 or the milestone x2 aka MX2.
and which version of android are you tring to root
your right this should be moved, that was my fault. I have the Dx2 and was looking to root 2.3.4 w
Sent from my DROID X2 using xda app-developers app
If this isn't what you need, please let me know.
http://d-h.st/O1b
MD5: d2ee3cd0995dfb830b2e6a8626fe2eda
Note: Though Dev-Host shows the uploader as anonymous, I assure you I'm the uploader for this given link.
Edit: For security, please note that the MD5 checksum matches the original MD5 which can be found here:
http://androidforums.com/3371672-post140.html
If the MD5, after downloading, does not match, try deleting the file and downloading again. If, after multiple downloads, the checksum still doesn't match, please notify me and I'll re-up the file.
Usage note: Make sure you've set the rooting script as executable or you're gonna have a bad time.
well, your not giving us much info, to work with
you can burn ezSBF for DX2 with root iso to a cd or usb flash drive
or the magic md5 root for muti-devices iso
I believe motofail linux version will root 2.3.4
or Dan Rosenberg's original Droid 3 root will
links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
---------- Post added at 01:02 AM ---------- Previous post was at 12:55 AM ----------
LaserChicken said:
If this isn't what you need, please let me know.
http://d-h.st/O1b
Click to expand...
Click to collapse
added to my list
Thanks
sd_shadow said:
well, your not giving us much info, to work with
you can burn ezSBF for DX2 with root iso to a cd or usb flash drive
or the magic md5 root for muti-devices iso
I believe motofail linux version will root 2.3.4
or Dan Rosenberg's original Droid 3 root will
links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
---------- Post added at 01:02 AM ---------- Previous post was at 12:55 AM ----------
added to my list
Thanks
Click to expand...
Click to collapse
Well, this thread is pretty old, but I thought I would report my recent experiences...
Motofail didn't work, but I used files from the motofail zip. I don't know if the above link is valid because I have motofail around from rooting my Droid 3.
My DX2 android version was at 2.3.5 and I used the sbf_flash executable from http://blog.opticaldelusion.org/
and a sbf file from https://sites.google.com/site/motosbf/droid-x2-sbf-files to sbf back to 2.3.4. Instructions I followed were at http://forum.xda-developers.com/showthread.php?t=1321061
I don't know if it was necessary to flash back to 2.3.4 or not; I was still finding my way around when I did it ... Actually, I was thinking that motofail would work if I had 2.3.4. But, no, it didn't.
So I did it manually, following the procedures in http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ starting at "The Exploit". All went well. I then had a superuser prompt following
Code:
sudo adb shell
Next, I looked in root_me_now.sh from motofail. I entered
Code:
adb="sudo adb"
and then hand entered (copied/pasted) all the commands after the line
Code:
echo "[*] Root successful! Persisting..."
I also could have just edited a copy of root_me_now.sh to gut the commands I didn't want.
Finally, I wanted to verify that Superuser and the su and busybox executables from motofail all work on the X2. I activated wifi, signed into google, downloaded a command prompt from the market, started the command prompt and typed "find". That worked, so I typed "su". As expected, Superuser asked if I wanted to give the command prompt root permissions. Then I had a root prompt. All good!
Oh, somewhere in there I had to google how to bypass phone activation so I could use the android interface on the X2. I lost the link, but big boys and girls can fend for themselves on that one.
NathanThern said:
Well, this thread is pretty old, but I thought I would report my recent experiences...
Motofail didn't work, but I used files from the motofail zip. I don't know if the above link is valid because I have motofail around from rooting my Droid 3.
My DX2 android version was at 2.3.5 and I used the sbf_flash executable from http://blog.opticaldelusion.org/
and a sbf file from https://sites.google.com/site/motosbf/droid-x2-sbf-files to sbf back to 2.3.4. Instructions I followed were at http://forum.xda-developers.com/showthread.php?t=1321061
I don't know if it was necessary to flash back to 2.3.4 or not; I was still finding my way around when I did it ... Actually, I was thinking that motofail would work if I had 2.3.4. But, no, it didn't.
So I did it manually, following the procedures in http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ starting at "The Exploit". All went well. I then had a superuser prompt following
Code:
sudo adb shell
Next, I looked in root_me_now.sh from motofail. I entered
Code:
adb="sudo adb"
and then hand entered (copied/pasted) all the commands after the line
Code:
echo "
[*] Root successful! Persisting..."
I also could have just edited a copy of root_me_now.sh to gut the commands I didn't want.
Finally, I wanted to verify that Superuser and the su and busybox executables from motofail all work on the X2. I activated wifi, signed into google, downloaded a command prompt from the market, started the command prompt and typed "find". That worked, so I typed "su". As expected, Superuser asked if I wanted to give the command prompt root permissions. Then I had a root prompt. All good!
Oh, somewhere in there I had to google how to bypass phone activation so I could use the android interface on the X2. I lost the link, but big boys and girls can fend for themselves on that one.
Click to expand...
Click to collapse
Root with Magic MD5 root
http://forum.xda-developers.com/showthread.php?t=1818758
[How To] Root DX2 2.3.5/1.3.418 magic md5 method
Sent from my Motorola RAZR MAXX using Tapatalk