Welcome to Flashe!:victory:
Flashe is basically an all-in-one installer which only requires a few clicks and you are root,unlocked(bootloader), and you can choose a recovery to install in the process. This is much easier than using ADB commands or fastboot.:good:
The program does included a feature that allows you to use a custom boot image and get rid of the "unlocked bootloader" screen.
WARNING: USE AT YOUR OWN RISK
Requirements:
-Atrix HD,Razr HD,Razr MAXX
- .bin logo file(rename to logo when put in flashe folder)
- .iso for your recovery(CWM,TWRP, or Philz)
Future Update:
-Downloads the required files from a server
-Menu(choose to install other things
-GUI, instead of text there is a actual button interface.
Errors:
You MUST allow the program to boot you into recovery otherwise the custom recovery is lost due to the android os overwriting it. If you have any other errors pm
me!
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Enjoy!
Alienware258 said:
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Click to expand...
Click to collapse
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I totally agree
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I looked at the threat, and it calls it a threat because it is a rooting tool.
Also,When I first started rooting I did not get how to use it at all(Mythtools).Instead I used programs on my android.So I made this to help new users coming to the atrix community once I finished learning ADB commands and some fastboot commands.
Here is the source:
Code:
adb kill-server
adb wait-for-device
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
adb reboot
adb wait-for-device
adb push unlock /data/local/tmp
adb shell chmod 755 /data/local/tmp/unlock
adb shell su -c /data/local/tmp/unlock
adb shell rm /data/local/tmp/unlock
adb reboot bootloader
fastboot getvar all
fastboot continue
adb wait-for-device
adb reboot bootloader
echo [-] To continue you will need a boot file which will
echo [-] replace the "Unlocked Bootloader" image. Name it:
echo [-] logo.bin
echo [-] Continue when you are in the bootloader and have the file.
pause
fastboot flash logo logo.bin
fastboot continue
echo [-] Processe complete!
echo [-] -Root installed
echo [-] -Bootloader unlocked
echo [-] ---------------------
echo [-] This next step will install a recovery.
echo [-] Recovery will allow you to install your own roms,etc(depending on the selected recovery)
echo [-] Rename your recovery image "rec" so it should be 'rec.img' then continue.
pause
adb reboot bootloader
echo [-] Continue once in bootloader
pause
fastboot devices
fastboot flash recovery rec.img
echo [-] Once finished flashing continue...
pause
adb reboot recovery
echo [-] Complete! You now should have recovery installed. Enjoy!
pause
Related
first of all iv been trying to root my legend for hours and this is geting very furstarting... i am using the guide here http://forum.xda-developers.com/showthread.php?t=845512
i have finaly managed to get adb to work and have made my goldcard after 2 days of intense work and now im trying to downgrade my phone to root it
i am geting the following error in adb
when i type adb remount it says remount failed operation not permitted i have looked all over the net and found no answer
in additon to that when im trying to use adb push i type the following
adb shell
$su
su
#adb push flash_image /data/local/
adb push flash_image /data/local/
i just get the same line repeated how to excute commands from adb? this is very confusing since im noob with rooting also the following lines i don't know how to excute them too
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
chmod 755 /data/local/flash_image
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
/data/local/flash_image misc /data/local/misc1-2.img
please explain to me how to use theese thanks!
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Click to expand...
Click to collapse
Read better, you have to open a new terminal for pushing the files to the phone, you can't use adb push while you are in adb shell.
BTW you should avoid posting questions in development section.
Disclaimer 1 : I tried to look for something like this but I did not found it. Then I tried to achieve it. Sorry if they are well known steps
This guide allows to root a Nexus One with unlocked bootloader with NO need to flash recovery
USE THAT INFORMATION AT YOUR RISK!!
Updated: Added a line to work with Gingerbread
That steps are for Ubuntu. If you are any interested windows user, please let me know.
Prerequisites:
Unlocked bootloader
adb working properly
1. Download fastboot
Code:
wget --referer=http://developer.htc.com/adp.html http://dl4.htc.com/RomCode/ADP/fastboot.zip
unzip fastboot.zip
chmod u+x fastboot
rm fastboot.zip
2. Obtain busybox (anyone have any direct link?) - NOT GOING TO FLASH CM, JUST GETTING busybox from a trusted place
Code:
wget http://download.cyanogenmod.com/get/update-cm-7.0.0-N1-signed.zip
unzip update-cm-7.0.0-N1-signed.zip system/xbin/busybox
rm update-cm-7.0.0-N1-signed.zip
3. Download su
-- UPDATE: that link broken, you have to donwload it from Google Play
Code:
wget http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
unzip su-2.3.6.1-ef-signed.zip system/app/Superuser.apk system/bin/su
rm su-2.3.6.1-ef-signed.zip
4. Download recovery-RA - NOT GOING TO FLASH IT, DON'T WORRY!!!
Code:
wget -O recovery-RA-passion-v2.2.1.img http://files.androidspin.com/files/amon_ra/RECOVERY/recovery-RA-passion-v2.2.1.img
md5sum recovery-RA-passion-v2.2.1.img
echo ... Validate md5sum is 3def709ab1c9e051a92a1c8b1504a36a
5. Reboot to bootloader - JUST BOOTING WITH, NO FLASHING
Code:
adb devices
adb wait-for-device
adb reboot-bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z `adb shell pwd 2> /dev/null` ]
do
sleep 1
done
6. Root it!
Code:
adb shell mount /system
adb push system/xbin/busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb push system/bin/su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/app/Superuser.apk
7. Reboot and enjoy rooting
Code:
adb shell reboot
Will this work on stock Gingerbread?
If you are running Nexus One with Gingerbread, as I understand, it can work. I've not tried, you can try.... at your risk ;-)
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
If you have an unlocked bootloader, yes, it will work. If you have an unlocked bootloader, you can install pretty much anything you want, whenever you want...
Sent from my Nexus One using XDA Premium App
Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
I've added a adb command (mount /system) to work with Gingerbread. It works on mine.
It also works on 2.3.4
Yep. Worked great for me. But with all due respect, it seemed a little fishy to me that your directions have users pull busybox from Cyanogenmod but then have them pull su and Superuser.apk from a random file on a Dropbox account especially since both files are available in the already trusted Cyanogenmod download that was used for busybox. And even more so because the Superuser.apk file using your instructions is a larger file than the one included with Cyanogenmod. So I only used the files from CM and it worked like a charm.
Not accusing you or anything. I'm just pointing that out.
The easier way is to do step 5, then flash the su zip from step 3, and you're pretty much done. You can install busybox through the Market app...
Don't worry for the link, I toke it from the original post for that su release:
http://forum.xda-developers.com/showthread.php?t=682828
I agree it's enough with CM but I intend to get the last version... may be it's not the best option...
Thanks for your comments.
This Guide is to root the LG Revolution 4G with system builds V7 and lower using only linux. Not many people use linux, but I do and figured someone may need a hand if they are just starting out with linux. I have tested this on 2 phones and 2 different distros. If you have problems let me know.
Android is based off from linux so let's do it in linux.
Disclamer
Do This at your OWN risk. Nothing is my responsibility if you brick your phone or damange anything in frustration. If you follow this guide to the "T" you should have no problems what-so-ever.
This is not MY exploit, only a guide on how to do it in a linux environment.
Things you will ABSOLUTELY need:
1) Root privliges on your linux-box
2) The exploit from mtmichaelson's post HERE
3) The Android SDK for linux HERE
4) Your LG Revolution, Duh!
5) Patience, and a brain
To start things off you need to setup the SDK, if you already have the SDK up and working skip down to the preparation section.
Setting up the SDK:
1) Go to your downloads folder and extract your android-sdk_xxx-linux.tgz
2) I recommend moving that extracted folder to your Desktop for easy access and rename the folder android-sdk.
3) Next you must download the proper platform-tools, so open terminal and type
Code:
cd /home/[your username]/Desktop/android-sdk/tools
sudo ./android
4) This should popup the SDK Manager, click on the checkmark for the tools folder then click "install _ packages"
5) Next go to your android-sdk folder and make sure you have the folder platform-tools. If not go back to "Setting up the SDK".
Preparation:
1) Make sure you turn USB debugging 'on' from Settings>applications>development>USB Debugging => This should be checked!
2) Make sure you have internet connection selected from Settings>Connectivity => select always ask or choose the default connection as internet connection.
Rooting:
1) Extract the exploit you downloaded above and I would recommend moving it to the Desktop for easy access.
2) Now connect your phone via USB, and choose internet connection when you click on the USB icon in your notifications pull-down menu; open up a terminal and type:
Code:
cd /home/[your username]/Desktop/android-sdk/platform-tools
sudo ./adb kill-server
sudo ./adb devices
3) This should give you a "List of the devices attached" to your computer with adb. Make sure you see numbers/letters and "device" like so...
Code:
99999B9999ECB9999 device
Note: if you do not get any devices listed, don't , do:
i) Disconnect your phone
ii) Pull the battery for 10 sec.
iii) Restart your computer
iv) go back to step #2
4) Now push the exploit and start it by typing:
Code:
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/zergrush /data/local/tmp/zergrush
sudo ./adb shell "chmod 755 /data/local/tmp/zergrush"
sudo ./adb shell "./data/local/tmp/zergrush"
5) This should start the exploit and you should see the activity in the terminal. When its done you should be prompted with a #.
a) if it is successful, simply click ctrl+Z. This should bring you back to a $ prompt.
b) if it fails
i) Disconnect your phone
ii) Backup ANYTHING you need with mybackup from the android market
iii) Perform a factory reset of your phone in Settings>Privacy>Factory Data Reset
iV) go back to step #2
6) Next we must push the proper files to run the root so type in terminal:
Code:
sudo ./adb shell /data/local/tmp/sh -c "mkdir /system/tmp"
sudo ./adb shell /data/local/tmp/sh -c "chmod 777 /system/tmp"
Code:
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/su /system/tmp/su
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/busybox /system/tmp/busybox
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/Superuser.apk /system/tmp/Superuser.apk
sudo ./adb push /home/[your username]/Desktop/LGRevolutionRoot/RevoToolkit-1.0.apk /data/local/tmp/RevoToolkit-1.0.apk
Code:
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/su /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/Superuser.apk /system/app/Superuser.apk"
sudo ./adb shell /data/local/tmp/sh -c "mv /system/tmp/busybox /system/xbin/busybox"
sudo ./adb shell /data/local/tmp/sh -c "mv /data/local/tmp/RevoToolkit-1.0.apk /data/app/RevoToolkit-1.0.apk"
sudo ./adb shell /data/local/tmp/sh -c "chown root /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "chmod 4755 /system/xbin/su"
sudo ./adb shell /data/local/tmp/sh -c "ln -s /system/xbin/su /system/bin/su"
sudo ./adb shell /data/local/tmp/sh -c "chmod 755 /system/xbin/busybox"
sudo ./adb shell /data/local/tmp/sh -c "/system/xbin/busybox --install /system/xbin/"
7) Everything should be in order now cleanup; type:
Code:
sudo ./adb shell /data/local/tmp/sh -c "rmdir /system/tmp"
sudo ./adb shell "rm /data/local/tmp/* 2>/dev/null"
8) Just left to do is reboot the phone so type:
Code:
sudo ./adb reboot
sudo ./adb kill-server
Congrats! now you should reboot and be completely rooted and have the RevoToolkit to install the CWM recovery.
To install the recovery just start the RevoToolkit app and check for stock recovery and then install CWM.
Then you are free to install proper ROMs/Kernels.
If anyone has any questions please tell me your distro and if you are running virtually or not.
Hope this helps!
Special Thanks:
mtmichaelson for posting the inital thread for the download of his repackaged exploit.
The The Revolutionary Guys for the exploit
djrbliss for the initial script and port
thecubed for RevoToolkit
MikesTooLz for coordinating
While I will probably never use my Linux box to root a phone (one clicks are so easier ) You are my hero for putting this together. A "thanks' to you sir!!
Anytime glad to see someone here uses Linux!
Sent from my SCH-I500 using XDA App
Zoookle said:
Anytime glad to see someone here uses Linux!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We all do every day
VS910 4G Kangwich
Lol yes we do, our phones
I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?
hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!
Hi, I'm a newbie to android rooting and have spent the whole day trying to root my Kindle Fire HD v7.2.3.
I've used the bin4ry RunMe.bat and RootQemu.bat. I have no problems with the Qemu part but as for the RunMe.bat part I get permission problems (see picture below)
http://www.freeimagehosting.net/ikz64
The device gets rooted but the super user is no where to be seen. Therefore I can access root files but I can't write as it is read only.
I've already tried this: http://forum.xda-developers.com/showthread.php?t=2086210 (fixing a bug)
I've also tried the basics of rebooting after rooting, run as admin, locate through cmd but nothing has worked for me so far.
Anyone know what the problem is?
I was having a similar permission denied error when rooting 7.2.3. Try this and see if it helps. These commands are pulled from the Qemu script.
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
Wait for the device to reboot then run these.
Code:
adb shell rm /data/local.prop
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
reboot
Now wait for the device to reboot then check if the Qemu root hack worked correctly by connecting to your device with adb shell. You should see a root prompt.
Code:
$ adb shell
[email protected]:/ #
If you see a root prompt then re-run the RunMe.bat script and it should complete without error. The reason for your permission denied error is the script is not running as root.