[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.
Related
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?
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Androidious said:
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Click to expand...
Click to collapse
I have. No reply. Prob busy.
Sorry bout the post location.
Sent from my HTC PH39100 using xda premium
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
gtkansan said:
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Click to expand...
Click to collapse
xHausx said:
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
Click to expand...
Click to collapse
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
joeykrim said:
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
Click to expand...
Click to collapse
All apreciated. They did use a similar method, http://forum.xda-developers.com/showthread.php?t=1345620
[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows] to get stick temp root. Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board. I would think with the huge board level similarities between the raider/vivid and all the sensations that someone would have some experience to lend an idea or three ... Any help would be REALLY Apreciated! Thanks everyone.
Sent from my HTC PH39100 using xda premium
gtkansan said:
Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board.
Click to expand...
Click to collapse
android exploits take a lot of work to find/test/develop/release. bootloader exploits are generally more time/labor intensive to find/test/develop/release as bootloader code is closed source compared with android code that is open sourced. in addition, bootloaders can be very specific to only a few devices, where as android is running on many devices.
bootloaders have to be reversed engineered which is a skill set not many people have.
after all that negative news, perhaps somebody with the skill set will take the time to examine this device. perhaps a previous method will work or hasn't been patched!
after reading the thread linked above, seems everybody is on the right track. hope the extra information helps. good luck!
I spent a lot of time batting my head against the wall trying to get native voice-mail to work on my Boost Evo 3D. Many questions and threads were found but no clear cut instructions or solutions were to be found. So when I finally got the native voice-mail notifications working I decided to pass along what I found. I hope this helps someone. I'd like apologize ahead of time if I did not put this thread in the right spot. I am not trying to take credit for anyone else's posts if any of this info seems familiar this is just a combo of what worked for me. From what I read this works for more than just Boost-Mobile. Anyway here is what I found and what I did.
You will need:
Root - For Evo, Unrevoked is recommended
http://unrevoked.com/
For Evo Shift, instructions to root are available on
http://forum.xda-developers.com/showthread.php?t=932153
ADB - Download and install the Android SDK
http://developer.android.com/sdk/index.html
Patched Phone.apk -
http://www.mediafire.com/?u0uabfzjkebyxk8
Start phone in recovery mode
To enter recovery, shut down phone then restart by pressing and holding
Volume Down and Power at the same time, then use the Volume buttons to select
Recovery. Performing a Nandroid backup is highly recommended.
Once in Recovery, mount /system
Copy Phone.apk from the "3.70.651.1" folder to where you've installed ADB
Run your system command/terminal prompt and change folder to where you've installed ADB (left shift and right click to start command prompt inside the android-sdk/platform-tools folder)
when you do adb shell if you get a $ prompt that means that you are with lesser user privileges, and you need to run the su command in order to get Root Privileges and continue with the rest of the commands (edit added thanks to megabiteg)
Run the following commands:
adb shell
cd /system/app
rm Phone.apk
rm Phone.odex
rm vtt-sprint.apk
exit
adb push Phone.apk /system/app/Phone.apk
adb reboot
Good Luck.
This only works for phones running 2.17.651.5
Please let me know if this helped you by clicking on thanks.
Thank you for this and the details. I am running into an issue though when I try to CD to App it tells me that it is unable. Yes I am fully rooted through HTCs method and Im running Teamwin backup. Any ideas whats up?
hacker1313 said:
I spent a lot of time batting my head against the wall trying to get native voice-mail to work on my Boost Evo 3D. Many questions and threads were found but no clear cut instructions or solutions were to be found. So when I finally got the native voice-mail notifications working I decided to pass along what I found. I hope this helps someone. I'd like apologize ahead of time if I did not put this thread in the right spot. I am not trying to take credit for anyone else's posts if any of this info seems familiar this is just a combo of what worked for me. From what I read this works for more than just Boost-Mobile. Anyway here is what I found and what I did.
You will need:
Root - For Evo, Unrevoked is recommended
http://unrevoked.com/
For Evo Shift, instructions to root are available on
http://forum.xda-developers.com/showthread.php?t=932153
ADB - Download and install the Android SDK
http://developer.android.com/sdk/index.html
Patched Phone.apk -
http://www.mediafire.com/?u0uabfzjkebyxk8
Start phone in recovery mode
To enter recovery, shut down phone then restart by pressing and holding
Volume Down and Power at the same time, then use the Volume buttons to select
Recovery. Performing a Nandroid backup is highly recommended.
Once in Recovery, mount /system
Copy Phone.apk from the "3.70.651.1" folder to where you've installed ADB
Run your system command/terminal prompt and change folder to where you've installed ADB (left shift and right click to start command prompt inside the android-sdk/platform-tools folder)
Run the following commands:
adb shell
cd /system/app
rm Phone.apk
rm Phone.odex
rm vtt-sprint.apk
exit
adb push Phone.apk /system/app/Phone.apk
adb reboot
Good Luck.
Click to expand...
Click to collapse
Luckypph said:
Thank you for this and the details. I am running into an issue though when I try to CD to App it tells me that it is unable. Yes I am fully rooted through HTCs method and Im running Teamwin backup. Any ideas whats up?
Click to expand...
Click to collapse
when you do adb shell if you get a $ prompt that means that you are with lesser user privileges, and you need to run the su command in order to get Root Privileges and continue with the rest of the commands.
Is this for the Evo Shift or Evo 3d? You have the rooting process for the Shift, but the phone.apk download is for the Evo 3d. Does the phone.apk work with the Shift? Im fairly new to the android scene.
Yes it should work for the EVO 3D, Evo Shift, Evo 4g. in the downloads there are specific inst ffor each type
hacker1313 said:
Yes it should work for the EVO 3D, Evo Shift, Evo 4g. in the downloads there are specific inst ffor each type
Click to expand...
Click to collapse
Thanks! Will try this later.
Need help with voicemail notification!
Hello,
I have been pouring over the forums trying to find a way to get my voicemail notifications working on my Evo 3D (rooted, flashed to Boost!)! This seems to be the method to use, but the problem I am having is this:
First of all, I am completely new to this, so alot of it is confusing to me! I am trying to follow the directions as best as I can, but it still seems difficult to me! Sorry.....complete noob here!
Secondly, when I try to run the ADB, it keeps telling me something like it's "not a valid command" or something to that effect! I'm not sure if I downloaded the Android SDK to the proper place or not (think I just created a new folder on my desktop and placed it in there?)! Is there a specific location that I should download it to?
Lastly, if you could put down the instructions in very simple, plain terms, that would be great! Maybe they already are, and I apologize if thats the case, because like I said, I am VERY new to this! It just seems like I'm missing something here, and I don't want to mess my phone up in any way, shape, or form! Thanks so much for any help that you can offer in this matter! I NEED my voicemail notifications working, so I know when I have voicemails! I already missed an important message, and I don't want to miss anymore! Thanks again!
Edit: I just noticed this message in the "tools" folder of the Android-SDK file:
"The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location".
Could this be the issue that I am experiencing, and if so, how can it be corrected? Again, I am really "computerally challenged" here, so be specific! LOL! Thanks again!
Nobody? Is this issue dead now, or what? Guess I'll do without voicemail!
Copasta said:
Hello,
I have been pouring over the forums trying to find a way to get my voicemail notifications working on my Evo 3D (rooted, flashed to Boost!)! This seems to be the method to use, but the problem I am having is this:
First of all, I am completely new to this, so alot of it is confusing to me! I am trying to follow the directions as best as I can, but it still seems difficult to me! Sorry.....complete noob here!
Secondly, when I try to run the ADB, it keeps telling me something like it's "not a valid command" or something to that effect! I'm not sure if I downloaded the Android SDK to the proper place or not (think I just created a new folder on my desktop and placed it in there?)! Is there a specific location that I should download it to?
Lastly, if you could put down the instructions in very simple, plain terms, that would be great! Maybe they already are, and I apologize if thats the case, because like I said, I am VERY new to this! It just seems like I'm missing something here, and I don't want to mess my phone up in any way, shape, or form! Thanks so much for any help that you can offer in this matter! I NEED my voicemail notifications working, so I know when I have voicemails! I already missed an important message, and I don't want to miss anymore! Thanks again!
Edit: I just noticed this message in the "tools" folder of the Android-SDK file:
"The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location".
Could this be the issue that I am experiencing, and if so, how can it be corrected? Again, I am really "computerally challenged" here, so be specific! LOL! Thanks again!
Click to expand...
Click to collapse
this guide is perfect!! (thanks OP!!!). you have to learn how to setup and install adb....there r a million guides on doing this and checking to c if u have it installed correctly. just google it n u should b good...agn this guide is perfect n easy once u have adb installed correctly...
Success finally!
strive53 said:
this guide is perfect!! (thanks OP!!!). you have to learn how to setup and install adb....there r a million guides on doing this and checking to c if u have it installed correctly. just google it n u should b good...agn this guide is perfect n easy once u have adb installed correctly...
Click to expand...
Click to collapse
Thanks so much for the google search suggestion! I did it, found what I was looking for, took a deep breath, and two days later FINALLY figured out how to do this correctly! Funny thing is, I'm not even sure how I did it! LOL! Probably a good idea to not know too much, so I can't mess up too much! Thanks again SO MUCH for this tuturial....my voicemail notification works perfectly now! You guys are the best!
Shouldnt this method work root explorer or terminal emmulator, and does your rom have to be odexed or deodex? I get a lot of noobs contacting me who for the life of them can't set up adb even after reading the through the forums, i want to make this easy for them by trying alternate method but i know eventually everone should learn how to use adb
The guide is perfect. I am new at this but I accomplished it just fine. Also just a little help for other newbies. Make sure debugging is checked, and fastboot is unchecked. Also when you plug in your phone, you can have the android OS running. Also when you type adb shell, if you get a # sign you have root access and type the commands exactly as the guide states. Thanks Hacker1313!! you ROCK
==================================================
Device: HTC EVO 3D AKA 3VO
Rom: ZR3Dv2.2A
Kernel: Stock
Recovery: 4EXT
Baseband: 1.06.00.1216
Build Number: 2.17.651.5 CL245066 release-keys
Android Version: 2.3.4
HTC Sense Version: 3.0
H.Boot 1.5 Unlocked
S-On
I tried this multiple times and I keep getting "com.android.phone has stopped unexpectedly" force close. =/ How do I fix this?
EDIT: Nvm I have fixed it I pushed a different phone apk over the one that was force closing, and it is now working perfectly again with the native voicemail I have an Evo 4g on The Classic v0.0.9 rom. this is the apk I used:
http :// www . mediafire . com /?9te746ctx1j9xxi
anna.molly said:
I tried this multiple times and I keep getting "com.android.phone has stopped unexpectedly" force close. =/ How do I fix this?
Click to expand...
Click to collapse
Wat Rom u on?
Sent from my EVO 3D S using XDA
strive53 said:
Wat Rom u on?
Sent from my EVO 3D S using XDA
Click to expand...
Click to collapse
Hi, I edited my post with an update thanks for trying to help. The OP did say it should work with an Evo 4g but it sure didn't work on mine! lol
As an update to my earlier post, Well, it worked for less than a day, then i couldn't receive or make calls, said my account was invalid, error code 67, and even my phone profile was completely screwed up to the point someone elses number was appearing on my phone info. took me hours to fix the problem, and the only thing I had done recently was push that phone.apk to my EVO 3D. So I am wondering if there is an updated phone.apk for the EVO 3D?? Any help would be great I loved my native voice mail working on my 3VO flashed to boost, for the short time it lasted.
Device: HTC EVO 3D AKA 3VO
Rom: ZR3Dv2.2A
Kernel: Stock
Recovery: 4EXT
Baseband: 1.06.00.1216
Build Number: 2.17.651.5
Android Version: 2.3.4
HTC Sense Version: 3.0
H.Boot 1.5 Unlocked
S-On
Dmoneyxxxx said:
As an update to my earlier post, Well, it worked for less than a day, then i couldn't receive or make calls, said my account was invalid, error code 67, and even my phone profile was completely screwed up to the point someone elses number was appearing on my phone info. took me hours to fix the problem, and the only thing I had done recently was push that phone.apk to my EVO 3D. So I am wondering if there is an updated phone.apk for the EVO 3D?? Any help would be great I loved my native voice mail working on my 3VO flashed to boost, for the short time it lasted.
Device: HTC EVO 3D AKA 3VO
Rom: ZR3Dv2.2A
Kernel: Stock
Recovery: 4EXT
Baseband: 1.06.00.1216
Build Number: 2.17.651.5
Android Version: 2.3.4
HTC Sense Version: 3.0
H.Boot 1.5 Unlocked
S-On
Click to expand...
Click to collapse
did you set the permissions on the apk?
I have pushed this phone.apk to about 7 or 8 Boost 3VO's without any issue and native voicemail works everytime. How long was you Boost 3VO working before you pushed the phone.apk?
There is nothing in the steps to the guide I posted that would change the meid or esn. The only thing I can think of is that something you may have missed a step when u flashed ur phone. I dont think I can get into too many specifics on that subject without breaking forum rules
Sent from my PG86100 using XDA
I used adb to push it to my 3VO, Idid not think I had to change the permissions of the phone.apk if I did it that way. It had been a good two weeks that my 3VO was flashed before i pushed the apk
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
I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
premo15 said:
I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
Click to expand...
Click to collapse
the top right there is a search box.. type your question in there and im sure u will find your answer
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
I have searched...extensively But I haven't been able to find any detailed information regarding my questions. Lots of general information about flashing su packages, etc. but I'm interested in how it works from a developer's perspective. I've read conversations between developers regarding su binaries but because they already have a mutual understanding of what they're discussing, it tends to be a little over my head.
Did the basic info site I provided help you understand
/
Rxpert said:
Did the basic info site I provided help you understand
/
Click to expand...
Click to collapse
Yes, it's a good start, thank you. One thing that's still throwing me though is that I've read some posts from people using one of the automated methods that say it completed partially (i.e. the bootloader was unlocked) but didn't actually root. When they attempted to install SuperSU manually, it complains about not having root access. Is that because they only have the apk and not the binaries? Do the binaries not get installed at the same time? Is that what flashing the Evo4GLTERoot.zip does?
Sent from my EVO LTE
Rxpert said:
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
Click to expand...
Click to collapse
Ok, went back and re-read a bunch of stuff with the understanding I gained from that article and it's starting to make sense now. Just one last question: when you install a custom "rooted" ROM, I assume that means that it has the su binaries and apk baked in. If that's the case, then really all you would need to do to gain root access is unlock the bootloader, flash a custom recovery and flash the rooted ROM. Is that correct?
Thanks again...
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
michael.stollaire said:
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Alright, I get it now! Thanks guys!
Mike, I'm already at my thanks limit today so I'll hit you up tomorrow. Out of curiosity, my limit seems kinda low (8)...does that increase as you gain seniority?
Yes, I believe u get infinite thanks capability, as ur XDA stature increases, although not entirely sure, to be honest.
A written thx is more than enough for me, BTW, and happy to help. Feel free to PM me with other inquiries, if u feel this will hasten ur getting answers and/or mitigation of outstanding issues.
Rock on!
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Rxpert said:
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Click to expand...
Click to collapse
Ah, good to know, "thanks" for the info...
Sent from my EVO LTE