Related
OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.
Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium
Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium
Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.
okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?
@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.
Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium
There are some noob tutorial around, but none of them specifically says
anything about 4.5.141 unless you dig quite some pages at the end of the
threads. This post is not going to be a complete guide or tutorial, nor it is
going to be a detailed how-to. It will be a breif how-to that tells you what
works on 4.5.141 and give you some confidence when rooting and unlocking
4.5.141.
Before flashing a new rom on your stock atrix, you should understand the risks
of losing data, voided warranty, malfunction of the new rom, or even get your
phone hard bricked. if you were worried, and still are worried after reading
many XDA threads, a new rom is not for you. The stock ROM is not that bad.
Enough talk, let's get to the point of how to get CM7.2RC2 running on your
phone.
Table of Contents
1 PRE-CONDITIONS
2 BRIEF PROCESS
3 DETAILS
1 PRE-CONDITIONS
Atrix phone.
Stock rom running 4.5.141, stock bootloader.
If you have rooted your phone, or have unlocked your bootloader, just skip
the corresponding step.
If you are running versions below 4.5.141, there are ready-made scripts to
do things.
I myself use an SD card, but I don't think it's necessary to flash
CM7.2RC2 or gapps. (Please correct me if I'm wrong.)
Windows OS.
Motorola only offers phone drivers to Windows OS.
Internet access.
You will need to download files from some file sharing websites.
USB Cable.
For connecting your phone to Windows PC and run commands.
Know how to run a command line application in Windows.
I won't tell you how to use unzip, cmd.exe, and cd commands. I won't tell
you about PATH, directorys and file names. If you are looking for a
word-by-word tutorial, stop now.
2 BRIEF PROCESS
Download CM7.2RC2 zip file and gapps.
Backup important user data.
Root your phone so that you can run Titan Backup.
Backup all your data, including app data that you wish to keep.
Unlock bootloader.
[Root again &] flash recovery. //read why I root again in details.
Flash rom and gapps.
Config CM7.2, restore app data.
3 DETAILS
Before I start, I need to say I only own an AT&T atrix, other atrix could have
some differences, please read the threads that I refer to to get more
information.
Download CM7.2RC2 zip file and gapps.
CM7.2RC2
http://download.cyanogenmod.com/?device=olympus
download update-cm-7.2.0-RC2-olympus-signed.zip
gapps
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
download the one for CyanogenMod 7.
Store CM7.2RC2 to your internal storage.
Store gapps to your SD card. [I don't know why.]
Store them to both place if you are unsure. [That's what I did.]
On stock rom, internal storage is mounted at mnt/sdcard, SD card is
mounted at mnt/sdcard-ext.
# Could someone tell me why where to store the zip file matters?
# I see Romracer's Recovery can flash zip file in either place.
Back up important user data.
Everyone has different things to back up.
My list includes:
Contacts.
App settings & data
if the app support "backup to SD card" alike function, do it.
if the app support syncing, do it.
this includes syncing all items on google account.
for other apps, you may use Titan Backup later to backup data.
bookmarks.
ssh keys stored on phone.
icons on Home screen.
a list of installed apps.
Photos/Camrecords.
Musics
PDFs
network and VPN settings
I purposely do not mention apps I am using to avoid advertising.
Root your phone so that you can run Titan Backup.
I don't think rooting your phone is necessary at this stage, but I did it
in order to use Titan Backup. If you have nothing worth backing up, you may
skip this. (Please tell me if I'm wrong here.)
[install Motorola USB drivers]
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
download the all-in-one driver and install it.
[download the tools and preinstall.img file.]
http://hotfile.com/dl/147091460/bb5f4c5/moto-fastboot-win32.7z.html
download the 7z file, and unzip it using winrar or 7-zip.
7-zip is free software, google it for download.
boot to fastboot mode.
Power off your phone. hold Volume Down, press Power.
when the screen show fastboot, press Volume Up to enter fastboot mode.
(Press Volume Down will cycle all mode choices, press Volume Up selects the
mode that is shown on the screen.)
flash preinstall, reboot.
unzip the 7z file you downloaded, start cmd.exe and go to that dir.
connect phone to Windows PC using usb cable.
run these commands:
Code:
moto-fastboot flash preinstall preinstall.img
moto-fastboot reboot
replace /system/bin/su with /preinstall/su and set permission to 6755.
when phone is fully rebooted, enable USB debugging.
Settings > Application > Development > USB debugging
Disconnect and reconnect the cable if windows does not find your phone.
run these commands:
Code:
adb shell
/preinstall/dosu
/bin/mount /system -o remount,rw
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
exit
exit
Notes:
If "adb shell" fails, try disconnect and reconnect cable.
On success, it shows "$" on a new line.
when running "/preinstall/dosu", you can ignore this error:
"bash: groups: command not found".
done.
now you are rooted, you can disconnect USB cable if you wish.
Backup all your data, including app data that you wish to keep.
More backups won't hurt. Now it's time to backup all your apps and files.
Now that you are rooted, you can install Titan Backup and backup the
non-system apps. Back up other apps as you wish. I'm completely new to
Titan Backup. I only used it to backup non-system apps, for the purpose of
restoring app data later.
Note that CM7.2RC2 is based on android 2.3.7, while 4.5.141 is based on
android 2.3.6. I did not try to restore 2.3.6 stock app data to 2.3.7
myself to avoid any possible error.
If for some reason, Titan Backup told you you are not rooted, just do the
root step again. It does no harm to your phone.
Unlock bootloader.
[install motorola USB drivers]
if you haven't done this. Do it now. see download link at step 3.
[download RSD, fastboot, and the small 1MB SBF file.]
moto-fastboot is included in the 7z file in step 3.
RSDLite and the 1MB SBF file download:
http://forum.xda-developers.com/showthread.php?t=1136261
scroll to the "Unlock:" section.
"Unlocker only SBFs - These small 1mb SBF files will get your phone ready
to fasboot oem unlock. They are the files most people should use."
Notice that the 1MB SBF file is different for ATT and other atrix.
Choose the correct version.
Power off atrix. take out microSD card and sim card. [not sure why]
Flash the small SBF file using RSD Lite.
Unzip the downloaded small SBF file.
Install RSDLite.
Boot phone to RSD mode. Connect USB cable. Run RSD Lite on Windows PC,
select the unzipped .sbf file, press Start.
[I guess you know how to boot to different modes now. But just in case,
first Power off your phone, hold Volume Down and press Power, when screen
show "fastboot", press Volume Down to cycle between choices, when it show
"RSD", press Volume Up to confirm.]
The phone will disconnect and connect again and may goto other modes
automatically. Watch the progress shown in RSDLite window.
Here is a side story: while I'm flash this, the phone switch to fastboot
mode automatically, when RSDLite is waiting for the phone to go to BP
pass ?? mode, at progress 98%. I didn't notice it is still waiting for
the phone, when I see it goes to fastboot, I just run the fastboot oem
unlock command in the next step, and the phone get unlocked successfully,
then I reboot it with fastboot reboot. But when the reboot finished, the
phone asks me to setup moto blur and google account. apps and user
configs are gone. But I don't care, becaue I have all important things
backed up. I just skipped most of the setup because I'm going to flash a
new ROM. So it looks like the phone did a factory reset after the
unlock. I also lost root after this. Could someone tell me is this
expected behavior of a normal unlock, or is this a consequence that I
failed to let RSDLite work to the full 100% progress?
Do fastboot oem unlock.
Boot phone to fastboot mode. connect USB cable.
Switch to the dir that contains moto-fastboot, then run these commands:
Code:
moto-fastboot oem unlock //It will print your device ID.
moto-fastboot oem unlock <your-device-ID>
moto-fastboot reboot
Done.
When your phone reboot, you will notice the unlocked red text on motorola
screen.
I hope you did not get a factory reset. But if it did, don't panic.
[Root again &] flash recovery.
I definitely do not want to root again here, but my phone looks as if it
has got a factory reset when I was unlocking the bootloader. And I lose
root as a result. I could just go ahead and flash recovery, but it turns
out I need to delete a file in /system partition before I can boot into
Romracer's Recovery. To delete that file, I need root.
[download Romracer's Recovery]
http://forum.xda-developers.com/showthread.php?t=1204500
You can download any of the recovery file listed there under "ALL USERS".
To root again, just redo step 3.
Rename (or delete) /system/etc/install-recovery.sh using a root file
manager.
When you are fully rebooted, install a root file manager (for example, ES
file explorer), and rename /system/etc/install-recovery.sh to
install-recovery.sh.bak
Until you rename or delete this file, you can't boot into the recovery
you are going to flash. Because the recovery file will be replaced when
the phone boots.
flash recovery.
If you downloaded zip file, unzip it.
Then copy img file to the dir that contains moto-fastboot.exe.
Boot phone to fastboot mode, connect phone to Windows PC, go to
moto-fastboot dir, run these commands:
Code:
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
moto-fastboot reboot
Flash rom and gapps.
Preparation
If your battery is low, replace battery now. There is no stop and resume
support when making a backup or flashing a new ROM.
If you have taken out microSD card and sim card when unlocking
bootloader, you should put it back now.
Boot into recovery mode.
Inside recovery, press Volume Up and Volume Down to go up and down.
Press Menu soft key to confirm.
Do a backup.
Go to Backup & Restore and create a backup.
You will be asked whether to include webtop in the backup.
If you do, expect the backup to take a long time. (~30 minutes)
Flash CM7.2RC2 and gapps.
In recovery menu, choose install zip file from SD card.
Locate the CM7.2 zip file, and confirm flash.
When done, you need to wipe some data/cache, confirm wipe in each step:
wipe data/factory reset
wipe cache partition
Advanced > wipe Dalvik Cache
When asked whether to include sdcard-ext, I chose yes.
Done.
You are ready to reboot the CM7.2RC2.
Config CM7.2, restore app data.
Some configs you may want to tweak:
Home Screen > Menu > More > Wallpaper
CM settings > Display Settings > Screen-off animation > off
Display > Brightness > [auto]
Display > Animation > none
Date & Time > Select time zone
Sound > Phone ringtone
Sound > Notification ringtone
Sound > Haptic feedback > off //vibrate when pressing soft keys
CM settings > Sounds > Mute camera shutter
CM settings > Input > Long-press menu > soft keyboard
Some first impressions of built-in apps and the CM7.2 ROM.
The Motorola stock quickoffice is gone. you might want to instal Adobe
Reader for PDFs.
Stock gallery is unusable, it's worse than Motorola stock Gallery. Just
use Quickpic and set your image/photo directories.
ADWLauncher has 3 icons in the stock, you can change it to 5 icons.
ADWLauncher > UI Settings > Main Dock Style > 5 Icons
Now you can go ahead and install apps you use from Market(Google Play).
You can restore user app backups from Titan Backup.
Enjoy CM7.2
All credit goes to XDA members, CyanogenMod team and Motorola Corp for the mod, tools, files and drivers that they developed and released. Without them this how-to won't be possible.
This code is translated from org-mode text to html then to BBCode, I'm sorry if the formatting looks a bit alien.
Thank you for your great work (not found the thank button). I think this tread may be added to the top, found it only accidentally
Great thread for noobs! Bump so it doesnt get lost. Thanks for your time writing this.
HELPPP
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
jesusitox12 said:
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
Click to expand...
Click to collapse
Isn't the proper command "moto-fastboot" ?
MB860, CM7.2.0, Faux 026b1 1Ghz
jesusitox12 said:
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
Click to expand...
Click to collapse
perhaps after you unzipped the moto-fastboot stuff you didn't direct your command prompt to the directory?
or missing the path to it in system variables or something?
i remember i just have the directory with moto-fastboot in flash drive which i just navigate to in command prompt just to be able to run the moto-fastboot command
hope that helps?
I just got an N7 32GB tablet, very nice. I plan on rooting this device. Mine still on 4.2.1. What guide you guys recommend, both seem good so I'm undecided.
Thanks
Aut0botK1lla said:
I just got an N7 32GB tablet, very nice. I plan on rooting this device. Mine still on 4.2.1. What guide you guys recommend, both seem good so I'm undecided.
Thanks
Click to expand...
Click to collapse
Do you know how to use adb/fastboot ? if you know you can use that to easily root the N7.
Here's the link on how to use adb/fastboot to unlock and root the Nexus 7.
If not, then use this toolkit by following the link below:
http://forum.xda-developers.com/showthread.php?t=1766475
Download the program and install it.
After that, watch this tutorial first once and then start rooting with the toolkit.
http://www.youtube.com/results?sear...0.219.737.0j3j1.4.0...0.0...1ac.1.NbcxhPx0ZLs
IMPORTANT NOTE: You must unlock your Nexus 7's bootloader in order to proceed with the rooting process. As a result, everything in your tablet will be erased. So backup what you can and put it back later.
I would recommend using adb fast boot method, it is very simple if you follows it correctly, I will give you full instructions on how to unlock boot loader and root
ALL DATA WILL BE LOST , BACKUP EVERYTHING
I RECOMMEND USING TWRP CUSTOM RECOVERY
Getting started
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
Setting the Stage
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools") copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper") I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver") and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
+ Above.
Way to wordy and not easy to follow
Basically:
Boot into recovery (yes i know you don't properly have one)
Get Android SDK from HERE
Once downloaded/installed.
Navigate to the "Platform-tools" folder, where you should see ADB/FASTBOOT
Hold shift, right click and "open command prompt here"
type fastboot devices
(if your device is listed, move on)
Unlock your bootloader
type fastboot oem unlock
Download THIS(supersu)
Download TWRP from HERE
Place the SuperSU download file on your SD CARD (Nexus has a virtual SD, place it there)
Place the recovery in the "Platform-tools" folder with your ADB/FASTBOOT files.
Reboot to fastboot again (Power and volume down)
fastboot devices
if listed continue:
fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img
Reboot back into recovery (which should now be twrp) (POWER AND VOLUME DOWN)
Then from TWRP menu choose "Install"
Find the 2 files you downloaded and placed on SD card
Install them using TWRP.
Reboot
Profit.
Wilks3y said:
+ Above.
Way to wordy and not easy to follow
Click to expand...
Click to collapse
Well... I liked it... for a guy with only 2 posts to his/her name to explain (perhaps in TOO much detail) how to root takes b**ls:!
Keep it up, naman14... but be a little more judicious in what you include (and choose to exclude) in your walkthrou's.
Writing instructions is art in itself... and requires practice. Succinct and pithy is the way to go.
Rgrds,
Ged.
Thank you all, the last thing i ever rooted was my sprint htc hero a yr or so ago
You can easily root the SmartQ Z1 (W1) ZWatch by modifying the firmware and updating it to the watch. I don't know of any rooting tool (like framaroot) that does the job on the watch without flashing the firmware.
[CREDIT TO GEEK78]
(1) READ the [HOW TO] in this thread by geek78 who first made a root firmware.
Download his rooted firmware HERE
Extract it with WinZip or similar zip utility - you should see files and folders which include "system"
Go to "system" -> "app". Copy "superuser.apk" to somewhere else in your computer (and remember where it is)
Go to "system" -> "xbin". Copy "su" to somewhere else in your computer (and remember where it is)
==========================================
(2) Go to Smartdevice website and download the latest firmware - HERE
Extract it with WinZip or similar zip utility - you should see the same files and folders of (1)
Copy "superuser.apk" and paste it into the "system/app" folder of this unzipped new firmware
Copy "su" and paste it into the "system/xbin" folder of this unzipped new firmware, replacing the original "su" file
[OPTIONAL]
(a) If you want to remove any apps in the original firmware, you can rename them from "xxx.apk" to "xxx.apk.bak" (eg. I don't use Weather sync app (IndroidWeather.apk), Sleep app (SleepAnalysis.apk) and Health app (SmartQWatchHeath.apk)), before the following step
(b) You can also add your own apps into the system/app folder, so that you don't need to install them after updating to the new firmware
==========================================
(3) Open WinZip or similar zip utility and navigate to the folder that contains the unzipped firmware files and folders. Highlight all the files and folders ("META-INF", "system", "boot.img", "mbr-xboot.bin", "recovery.img"), and use your zip utility to compress them back into a ZIP file called "update.zip"
==========================================
(4) BEFORE FLASHING THIS MODIFIED FIRMWARE, you must follow geek78's steps:
[HOW-TO]
1-Flash the watch with the restore tool from https://hotfile.com/dl/255788947/abfedd9/z1_restore_tool.zip.html (yes, i know, it will format the watch and you will loose everything... but it is needed)
2-Copy the rooted firmware called "update.zip" to the root of the /Sdcard of your watch
3-Start the flash from the watch
4-After the boot you can delete the 2 chinese apps with App Uninstaller
Click to expand...
Click to collapse
*** YOUR MUST USE THE RESTORE TOOL TO CLEAN THE WATCH BEFORE FLASHING THE ROOTED VERSION OF A NEW FIRMWARE ***
Thanks bro I already knew this but just wanted to thank you for your time and effort writing these instructions for everyone
Sent from my SPH-L900 using xda app-developers app
help with restore tool
Hello I have been searching through the forums and got a little help but need more. I am having problems rooting my watch. I dl'd the restore tool, problem is one of the restore tools instructions was to install the driver in a custom path but my comp keeps auto dling the driver and I cant choose the path to install. I run the restore tool and try to boot into restore mode so the tool will recognize it but it wont do anything. What am I doing wrong and do you guys have any solutions for the install path and getting into restore so I can use the tool? Thanks in advance for your time.
techgeek191 said:
Hello I have been searching through the forums and got a little help but need more. I am having problems rooting my watch. I dl'd the restore tool, problem is one of the restore tools instructions was to install the driver in a custom path but my comp keeps auto dling the driver and I cant choose the path to install. I run the restore tool and try to boot into restore mode so the tool will recognize it but it wont do anything. What am I doing wrong and do you guys have any solutions for the install path and getting into restore so I can use the tool? Thanks in advance for your time.
Click to expand...
Click to collapse
Try finding the watch in Device Manager and updating the driver manually. The driver is in this folder on Win7 x64: C:\Program Files (x86)\Smartdevices\Z1 Burn Tool\driver\x64
jatkins09 said:
Try finding the watch in Device Manager and updating the driver manually. The driver is in this folder on Win7 x64: C:\Program Files (x86)\Smartdevices\Z1 Burn Tool\driver\x64
Click to expand...
Click to collapse
Thanks for your help I tried that and it didn't work sadly. I will just have to try another comp. I have tried going to restore mode with the watch off and with it on .Do you happen to know if i did a factory restore from the watch and then used the rooted 2.2 rom from geek78 if that would work or do i absolutely have to use the restore tool to wipe first?
techgeek191 said:
Thanks for your help I tried that and it didn't work sadly. I will just have to try another comp. I have tried going to restore mode with the watch off and with it on .Do you happen to know if i did a factory restore from the watch and then used the rooted 2.2 rom from geek78 if that would work or do i absolutely have to use the restore tool to wipe first?
Click to expand...
Click to collapse
Yes according to geek78, you must use the restore tool everytime you are installing a customized firmware. I guess the reason is that the restore tool wipes everything on the watch, allowing a clean new install.
I had no problem with installing the restore tool. When I uninstall and reinstall the tool, it remembers where the driver was, therefore I could not reproduce your problem. The best way is to try to install it on another computer eg. XP or Win7 32 bit (I heard that the 64 bit gives most problem with drivers).
If this fails, you can try (I have not tested and won't test because it is a hassle to reinstall all the apps!) to wipe the watch in recovery mode (which is really a modified CWM):
(1) You have to trick the watch to reboot into recovery first -
Find ANY file and make a zip from it called "update.zip"
You should test and see if this method works first, therefore download an official firmware from HERE - rename this file "update1.zip" (or anything other that "update.zip").
Connect your watch to your PC and transfer both files to the root of the watch.
On your watch: "About" -> "Firmware upgrade". Upgrade will fail and the watch will reboot in recovery mode.
(2) If you are familiar with CWM, you should know how to wipe user data, cache, dalvik and system. If not:
Use lower button to navigate (you can only go down, but it will circle back to the top) and upper button to execute.
Go to each of these and follow instruction to execute (choose "++++++++++ Go Back ++++++++++" to previous menu for the next item)
"Wipe data/factory reset"
"Wipe cache partition"
"Advanced" -> "Wipe dalvik cache"
"Mounts and storage" -> "format /system"
Then go back to main menu and choose "Apply update from nand" -> "choose zip from nand" -> choose "update1.zip" (or whatever name you gave to the firmware)
OPTION: you can wipe cache and dalvik again after installation (recommended by many modders)
"Reboot system now"
If update of the original firmware is successful, this means you passed the test. Now you can repeat the process using the rooted and modified firmware as "update1.zip".
THERE IS NO GUARANTEE THIS METHOD WILL WORK, but I think it should.
Got it
Ok i finally got it. The 32 bit was the key. Thanks so much for the help. Loving it, gonna root 2.3 and install.
Recovery mode tested and working :good:
Did follow your instructons could not go back after mounts and storage step. With re-boot watch seems to brick. HELP!
Ton.dewaal said:
Did follow your instructons could not go back after mounts and storage step. With re-boot watch seems to brick. HELP!
Click to expand...
Click to collapse
What is happening after you format? Is the "go back" option not available? Or is it there, but the buttons no longer navigate?
Sent from my HTC One using Tapatalk
"go back" option was available brougth me back to Mount & Strorage. Have ttried restore tool on two window machines (7 & 8) tool won't find watch. I'm bricked!
Ton.dewaal said:
"go back" option was available brougth me back to Mount & Strorage. Have ttried restore tool on two window machines (7 & 8) tool won't find watch. I'm bricked!
Click to expand...
Click to collapse
The restore tool has issues with most 64bit machines. If you don't have one, you're best bet is to find a friend or family member that has a running XP system. OR, do you know how to create a dual boot on a pc?
Sent from my HTC One using Tapatalk
Thanks for advise, have now 32 bit XP avaialble. Will test this evening Central Europe Time. Fingers Crossed
Installed on 32 bit XP machine restore tool 1.0.0 windows restart: no luck. Tried to install Usb_Boot_Driver.sys but get Installed failed (unsigned) message. Any advise?
Ton.dewaal said:
Installed on 32 bit XP machine restore tool 1.0.0 windows restart: no luck. Tried to install Usb_Boot_Driver.sys but get Installed failed (unsigned) message. Any advise?
Click to expand...
Click to collapse
That doesn't sound correct...send me a PM...I will give you the login info to my FTP. I have the latest release of the burn tool in exe format on there...you need to download that.
Sent from my HTC One using Tapatalk
I can't root the watch
I tried this method several times but didn't work. after I flashed modified room the watch start OK and I can see superUser icon although the watch still not rooted, because I can't connect using: adb shell su or adb shell root.
I used a v3.5 firmware, please help me someone knows other method to root the z1 watch?
thanks in advance
morbid01 said:
I tried this method several times but didn't work. after I flashed modified room the watch start OK and I can see superUser icon although the watch still not rooted, because I can't connect using: adb shell su or adb shell root.
I used a v3.5 firmware, please help me someone knows other method to root the z1 watch?
thanks in advance
Click to expand...
Click to collapse
Download Maja's DJDroid 6.0 rom (v3.5) , its rooted already
Bad links
Can somebody post those Superuser.apk and su binaries? The download link to geek's rom is bogus and is forcing me to download a bunch of junk.
I have the latest Kitkat firmware (3.7) and stock ROM already has su binary thru adb. My question is can I replace those files thru adb without packaging a zip?
Thanks,
Hi!
Does anyone know how to add the remote camera function in 3.7 ROM? The latest ROM that had it appears to be 3.1. I could not find it as an APK, so I think it is somehow else embedded in the ROM.
BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18
Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.
Reserved
Works great on OEM 6.6, thanks for the tool!
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for
Does Works to unlock 7.4.2?
khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.
edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.
OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38
gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.