I've got a few questions about Gfree.
1. What is it?
2. Is it a part of Android SDK or do I get it as stand alone tool?
3. Do I use it on the phone or on the PC in the command mode?
thanks.
this may give you a clue:
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
if not try looking here: stfw
NO. I've been at that link already.
It does not explain what Gfree is.
It only says to use commands like this:# ./gfree -f -b hboot-eng.img -y recovery.img
No explanation.
And Google does not give any good links either.
bumping up.
G-free is an application to gain permanent root access to your phone. The commands are what determines what you want the application to do such as sim unlock, s=off and such.
Also it is a standalone tool but adb is used to push the file to the phone. Commands are done through terminal emulator on the phone.
lowandbehold - thank you very much.
So this is something like z4root or SuperOneClick -a stand alone rooting app...
It just needs commands through terminal emulator.
The same concerns Rage?
Related
When will it arrive?for 101 i mean
It won't happen until we get permanant root. No telling when that will happen.
a better question is, when will root be available, doesn't seem we have people with the right skills interested on the 101
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
adb push root/rageagainstthecage /data/local/tmp
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
./data/local/tmp/rageagainstthecage
Click to expand...
Click to collapse
It should kick you out and display some messages on the screen...just not errors. Then type:
adb shell
Click to expand...
Click to collapse
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
jerdog said:
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
It should kick you out and display some messages on the screen...just not errors. Then type:
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
Click to expand...
Click to collapse
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Tsusai said:
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Click to expand...
Click to collapse
Maybe have something to do with newer ARM architecture?
Sent with my fingertips and voice on my Evo
Why do you need permanent root?
Archos kindly released SDE which provides a way to install your own builds in dual boot.
Some links for more info:
http://forum.xda-developers.com/showthread.php?t=871335
http://www.openaos.org/
IRC #openaos on freenode
Maurice
The SDE require booting in recovery mode, and people said that it's often not perfect.
A permanent root for main OS would still be very useful, and still allow us to dual boot when we need to..
I think so too. PermaRoot would be very usefull.
Hey guys, I was wondering if anyone could tell me somewhere I could go to learn command prompts for the terminal emulator on our phone... I've googled it, but there's nothing there that im looking for... I wanna start to learn.. any help would be appreciated! Thanks in advance!
Sent from my SGH-T959 using XDA App
Learn some basic Linux commands.
Sent from my GT-I9000 using XDA App
Our phones are stripped versions of linux basically as stated previously
first type in "su" without "", so then you can edit your system files etc..
google some
some are
reboot
reboot download
reboot recovery
etc
xriderx66 said:
first type in "su" without "", so then you can edit your system files etc..
google some
some are
reboot
reboot download
reboot recovery
etc
Click to expand...
Click to collapse
Right, regardless of the two posts stating that Android is basically Linux being technically correct, you will find very few shell commands that actually work. Of the ones you do find, most of the switches and options will not work. The commands mentioned by xriderx66 are ADB commands, and you may have better luck concentrating on those. The phone does not have a full shell, it only has busybox, which is a stripped down version of a shell with most popular shell programs built in. The busybox on the phones are highly stripped down even for busybox. In fact this phone is the only shell I have ever used that does not even recognize the command switches for ls.
Here is an ADB tutorial.
So as the title suggests whenever I run the crackin.bat file in order to prepare my legend to be downgraded, it always displays the
cr--rw---- 1 1001 2002 90 line instead of the needed crwxrwxrwx 1 1001 2002 90 line.
I have looked everywhere to find a solution to this problem yet no matter where I look, everybody seems to be able to fix this by just either turning off and on their phone or wiping it. But I have tried all of those and, I have also tried doing this step on a different computer and reinstalling the needed files yet to no avail.
So if anybody has a possible workaround please do share it so I can finally root my phone after many tedious hours.
Sorry for the noob question and many thanks in advanced to anyone who can help me.
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11863394&postcount=2
Ahh, thank you. I had come across that before but i just didn't think that it would help! Silly me.
Ok, is there an IRC chat for the legend somewhere, im STILL getting this error. I can't find visionary+ anywhere where im sure enough its not going to mess up my phone, and i aparently am missing the files needed however none of the guides have downloads of everything i need.
PLEASE can someone help me? im so confused nothing is making sense. I get to copying files from DxDrx but that is nonexistant, what am i missing?
Ok, i got passed this step by doing these steps
1: download visonary here
http://forum.xda-developers.com/atta...3&d=1290501865
or here
http://content.modaco.net/dropzone/com.modaco.visionaryplus.r13.apk
or you can get it off the market
Then download hack4legend here http://www.multiupload.com/I3ZALKWB6A and unzip it somewhere (this is adb and the rooting tools)
2: install and open up visonary on your phone and do a temp root on your phone.
3: open up cmd and type in the following
cd "your hack4legend path here but with out the "" "
adb shell
su
4: after you do that on your computer you should see a notification on your phone come up, it might take a little. Accept it.
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
6: run the 1.31 RUU and your good.
Hope this helps
Unreal_628 said:
Ok, i got passed this step by doing these steps
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
Click to expand...
Click to collapse
/data/local/flash_image: not found
what am i doing wrong? i had to copy the contents of hack4legend to my adb folder so i have adb, is that it? do i have to change the drectory somewhere?
Mmm, if their is a platform tools sub folder in the android sdk try putting the hack 4 legend in there and re trying. It will either have to go in there or the tools sub folder in the android sdk.
And also make sure that when you use the cd command make sure to not just go to the android ask folder but into the platform - tools/tools depending on where you put your hack, try putting it in both and using different paths. Also you might wanna try updating the adb module "android sdk platform - tools revision 3" through the sdk manager.
And as allways make sure you have usb debugging on and have your phone connected to the computer through charge mode only.
below is a short preface and introduction before the main point of this thread. you can skip the preface if you want.
PREFACE/INTRODUCTION
i am relatively new here. i owned a nexus one a year ago and sold it for an iPhone 4. left the iOS world and jumped over to the "fastest phone in the world" (GS2 doesn't count yet). had my device for 3 days and i love it. jailbreaking iOS was very easy for me and i am *somewhat* comfortable rooting and unlocking bootloaders on android. Nexus One was very easy from what I can remember. fastboot oem unlock i believe it was? CWM, flashing *.zips, etc. So I would like to think I am not a complete n00b, but when it comes to motorolas, i have no experience. i currently own a macbook pro as my main computer, however, i do have limited access to a notebook running vista. now to get to my point of this thread.
***************************************
MAIN POINT OF THREAD: sbf_flash tool
SBF_FLASH (Mac and Linux) executable for flashing *.sbf files to motorola android phones in lieu of RSDlite. **ATRIX is said to be supported
link: http: //blog.opticaldelusion.org/2011_04_01_archive.html (wouldn't let me post real link, sorry)
*note: originally the developer wrote separate scripts for linux and mac as mac uses mach-o executables while linux uses ELF, however, the updated version works on both linux and mac platforms.
i searched the forums and only found 4 posts related to the tool sbf_flash and none of them were related to the motorola atrix. therefore i felt compelled to write this post and see if anyone has used this tool. if you read my preface it stated that I have a mac and only limited access to a windows computer therefore . my main question is. has anyone used this tool to flash *.sbf files to their atrix? if so, were there any issues whatsoever?
**if no one has used this tool before, I will hold my breathe and take the plunge. I will gladly be the guinea pig for all you mac/linux users out there (mainly mac users as if I am not mistaken, linux users have someway of flashing *.sbf files?)
thank you for reading this post. if I do not receive any input in terms of user's experiences with this tool by July 12th 9:00PM (EST), I will attempt to use it and see what happens. very anxious to get the bootloader on my device unlocked and flash CWM and flash 2.3.4. but i will wait.
**EDIT: i am aware of the fact that I can use bootcamp, VMware, Parallels or essentially any Virtual Box to run Windows on my mac and use RSDlite, however, I feel that if a simple executable such as sbf_flash worked, if would save a ****load of time/frustration/hassles.
I have used it
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
ionstorm3 said:
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
Click to expand...
Click to collapse
I run windows 7 on ny mac so... yea
Sent from my MB860 using XDA Premium App
thanks for all the input (from both of you). im assuming if i cd into the directory where the sbf_flash file resides I don't need to include the path every time? i have some knowledge of C and limited C++ or object oriented programming knowledge as well. i would love to use your script that automates the entire procedure if you don't mind giving it to me. once again thanks for the advice.
correct me if i am wrong, but chmod -x essentially gives the file permission to execute? trying to remember all the different unix commands. sudo, cd, and ls are only ones i use on a consistent basis
I have realized that it is not necessary to chmod +x the script file. All you have to do is include a ./ in front of it. For example ./sbf_flash filename.sbf. Btw saw your guide on how to sbf flash under *nix, so not sure if this information is still useful to you.
oh and yes cd, sudo and ls are the commands to use on a constant basis.
hey guys, kinda new to linux and the atrix. running 10.04 im not sure if i have the sbf_flash.sh. i have a file that shows as a shell script, i hope thats right. anyway. i have followed the direction above and cant seem to get it to run. this is what i have.
sudo chmod +x /home/serooted/Desktop/sbf_flash.sh
I in return get.No such file or directory. any ideas that would get me rolling? really want to get rid of the "unlocked" from my moto splash screen
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
ionstorm3 said:
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
Click to expand...
Click to collapse
Yes the sbf_flash does show up in the output. so my question would be, how now do i get it to flash the file?
is there any way that someone can post a step-by-step guide to unlocking the bootloader for the mb860 running 4.5.91 on a mac as i don't have access to a pc and am un able to find a clear method to doing so. sorry I'm new to this :/
OK, I just got an Amazon Fire HD 6 for free from a friend brand new so I figured this would be a great thing to learn rooting android and other things. No cost = no loss if I screw it all up.
Basically my goal is jut to root it to get it to be more like a regular old android tablet and not to have all the Amazon crap constantly running in the background sending all my info to Amazon every minute of every day. From reading here this seems possible. Please tell me if It's not.
Background:
I know quite a bit about PCs running Windows since 3.0 and have dabbled with Linux and Apache off and on over the years but I am by no means an expert. Advanced amateur might be better.
The tablet is running Fire OS 5.1.2. I don't know what it had when I first turned it on but I had no idea what I was going to do with it so I let it update itself until it got to the current 5.1.2.
I tried reading some of the tutorials but they seem way over my head as they seem to assume a knowledge of certain acronyms that I am not yet familiar with.
This is what I think I know so far. Please tell me if I'm wrong...
1. It is not possible to root 5.1.2. I probably should have left it at whatever it was when I got it which was probably 4.5.x.
2. Because of #1 above the only way for me to root this is to downgrade to 4.5.x.
Do I have that right so far? Because if I don't have at least that right then I am way off, so let's start there.
My goal would be for this thread to become a real "how to root your HD 6" for real total newbs like me. Step by step on what to download, from where, what is a TWRP what do you use it for, what is an ADB and what do you use it for, from turning the thing on to ending up with a nicely rooted tablet.
In case anyone else wants to know what happened and how I accomplished all, the answers are in page 6 of this topic ...
http://forum.xda-developers.com/fire-hd/help/help-thread-question-noob-friendly-t3206776
Here is a full tutorial in one place...
First off these instructions are for the Amazon Fire HD 6 gen4 running Fire OS 5.1.2 only. Will it work on other things? Who knows. Will it work on another of the exact same tablet? I have no idea. Would it work on this same tablet if I had to do it over again? Could be ... but then again, ya never know. So proceed at your own risk. All I know is that it worked for me here today on this particular tablet at this time and I hope I never have to do it again.
All of these instructions can be found at the following link at about page 6 of that topic.
http://forum.xda-developers.com/fire-hd/help/help-thread-question-noob-friendly-t3206776/page6
1: First I installed the USB driver from Amazon at the following link:
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
and then I downloaded the ADB SDK tools from links from this tutorial:
http://www.howtogeek.com/125769/how...roid-debug-bridge-utility/?PageSpeed=noscript
After enabling USB debugging on the device I had ADB ability.
2. Downloaded the Kingroot version 4.8.5 apk from here and ran it:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Let it go to town doing it's thing. Afterwards it claimed success and said that I was rooted.
3. Ran the following commands given by DoLooper from above xda post to disable OTA update:
Open a CMD window from folder with adb.exe by right clicking in that folder and holding down the shift key. Then run these commands one at a time:
adb -d shell "su -c 'pm disable com.amazon.otaverifier'"
adb -d shell "su -c 'pm disable com.amazon.device.software.ota'"
adb -d shell "su -c 'pm disable com.settings.systemupdates'"
Tried to rename OTA file from DoLooper instructions using Simple Explorer with root priviledges (not ES) - fail - does not seem to want to rename the file for some reason.
So at this point I was successfully rooted. But I basically had a virus running on my tablet called Kingroot . I checked using another app and I saw that it was constantly connected to China. Bad? I don't know but certainly does not making me feel all warm and fuzzy so next step was to get rid of Kingroot. Problem is that if you uninstall it it sets you back to unrooted default. So ... read on.
4. Installed Terminal Emulator for Android from http://www.apkmirror.com/
6. Uploaded the 4 files from the zip file from wolfdroid from second link in sd_shadow post in that same topic. Can be found here:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
7. ran the 2 commands from wolfdroid website using terminal emulator.
This removed Kingroot and left me rooted. Then I found an updated version of SuperSU and updated it too. So now I have a tablet that is rooted and I can install apps that require root access. Also I was able to uninstall some Amazon apps, disable others and basically stop it from phoning home.
BTW, I didn't recommend disabling com.settings.systemupdates. They do this on the 2015 Fires, but I have not used it on either the 2014s or 2015.
Yes, I apologize. You are correct. You did not suggest that one. That one I did get from the other topic. However, I did it and I don't see any negative effects so far.
But you know more than I so is there any reason you could see toward not doing that one?