This guide is compiled of various guides and threads that I've read and I want
to sum it all up in one post so you can root your HTC Dream (G1)
*many if not all rooting guides are incomplete or missing download links – I will do my best to keep links
posted and alive!
!!READ AND FOLLOW DIRECTIONS!! DO AT OWN RISK. I AM NOT RESPONSIBLE
FOR BRICKING YOUR PHONE.
I've compiled all of the files necessary and uploaded them to my drop
box
INDEX:
-|1|: Setting up adb and fastboot
-|2|: Rooting
-|3|: Changing hboot versions
-|4|: No recovery?
-|5|: Un-Root
*This guide assumes you are using Windows but Linux and iOS will be able to use most of it.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
First off thanks to Demkantor since he was my sensai in a way (wax on wax off style)
Then thanks to HTCDreamOn, EzTerry, Cyanogenmod and all the developers out there that make all of this possible!
This is the optional ADB and Driver setup. I recommend you follow it through as it would make things easier in the future. This is more a reference post.
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
1: ADB and Fastboot setup with HTC Drivers
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
In order to do certain things that pertain of flashing radios and hboots you are going to need ADB and
fastboot. This is also useful for The Google Bypass if you dont have data or an activated sim card.
Go ahead and download this zip
Extract the zip file straight to your local disk. (You should get something like this
afterwards "X:\Android" x being the letter of your local disk)
Now that you have that on your local disk. Go to X:\Android and install HTCDriver3.0.0.007.exe. (This
has most if not all HTC USB drivers)
Finally add a path in order to access ADB and Fastboot from cmd on the computer.
Click on the Start button and right click "My Computer" and choose
"Properties".
Now you should be in "System Properties" under the
"General" tab, go to the "Advanced" tab and click
"Environment Variables".
Now you'll be in "Environment Variables", Now under the
"System Variables" scroll down to "Path" and highlight
it by clicking on it and now click "edit".
IMPORTANT be sure to not delete ANY of the
variable values already in the "Variable Value" section. Now that that is
clear, go ahead and ADD this to the "Variable Value"
section: ";X:\Android" (Obviously replace X with your appropriate local disk letter and without
quotations)
You now have setup ADB and Fastboot.
But in order to use ADB and Fastboot you must go back to "Start" click or search
for run, type in cmd and you will now have command prompt open.
NOTE: I will not post what the command are since all you have to do is type in "adb" or "fastboot" in the command prompt and it will show you the sub
commands for each perspective command.
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
2: Rooting
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
-----------------
Step 1
-----------------
Assuming you're not on stock Android 1.0 follow steps 1-6, if already on android 1.0 skip to step 7 (1 when item is hidden).
This link is for RC29 (US)
*Optional is the update.zip as it seems to not work for some other wise you can skip the update.zip flash*
But if you need RC7 (UK) then use this link
Now plug in your phone and go to USB-MS. Go ahead and right click your USB-MS drive that appears
on your computer and hit "Format..". Now under file system be sure to set it
as FAT32 then hit format. Depending on how much memory your SD card is will
effect how long it will take. Once it is done move the DREAIM.NBH and update.zip into the
root of the SD card.
*only do this step if you got the update.zip file otherwise skip this step* Now power down your phone and boot up into Recovery mode (Home+Power).
You'll see an exclamation point with a triangle if you booted correctly. At this point
press "ALT+L" then you want to wipe all data so press
"ALT+W" then press "ALT+S" to
apply the update from the SD card.
Power down your device and boot it back up into fastboot mode (Camera+Power). It'll prompt you
if you'd like to install update hit prompted button and wait, this may take a bit and it won't be done
untill it prompts you that it is done so do not worry if it seems like its taking long and DO
NOT battery pull while it is installing.
Power down and now boot normally. You now have android 1.0 stock.
Sign-in into google.
GOOGLE BYPASS METHOD : only necessary if you do not
have data or an activated sim card or no sim card at all. But Wifi is required.
("<enter>" is actually the actual enter button so when it says "<enter>" press the enter button AKA return button)
Power on your phone but do not press anything. Plug your phone in via USB.
Slide your keyboard up type this is: "<enter>setprop persist.service.adb.enable 1<enter>". (Since you are on 1.0 this actually a command to enable USB Debugging although
you can't see anything)
Your pc will detect another device and begin installing drivers. (This is what HTC drivers installer was
for so your device will be installed correctly)
Now open cmd via run on your computer. Type in "adb devices" and it should show your device.
Example :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>adb devices
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>
Click to expand...
Click to collapse
(You only see this: "adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *" when its the first adb command your run when you open cmd)
type: telnetd<enter>
now on the computer using the command prompt type: adb forward tcp:23 tcp:23
then press enter
type: telnet localhost
press enter and you should see a # as you should have a root shell (while in this shell in order to backspace you must press the "Delete" button on your keyboard as pressing backspace will not do anything)
type: setprop app.setupwizard.disable 1
press enter
type: ps
press enter, this will show all the running processes
on the right column look for "com.android.setupwizard" then once that is located follow that line on to the second column from the left, the number in that column is the PID
type: kill PID
replace PID with the number that you found from the second column
It should now be at the home screen, if not press the "Emergency Call" button and press back and then you should be able to unlock the phone with the "Menu" button.
Now you can go to the settings connect with wifi and then bring down the notification that says you need to set up your account to sign in with your google email
Go to the market and download "TelNet" app. Once you have
it installed, go to USB-MS and put this recovery image onto the root of your SD card. reboot your device but do not press
anything or unlock the screen.
Once booted up slide your keyboard up, will unlock the device, and press the enter button twice and
type this in "telnetd" then hit enter (It’ll be a contact search but it’s okay). Now
go open Telnet app, and hit connect. If you did the telnetd part correctly you
will be prompted with a #. Otherwise you'll get a connection failed message, if
so reboot device and attempt the telnetd command again.
Type these commands in on your phone:
Press enter after each line
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
You now successfully flashed Amon_RA_ Recovery. :good:
You may reboot into your new recovery (power on holding home button) and flash a custom ROM. But
I do suggest upgrading your bootloader and radio first as the amount of ROMs available to you will be
much greater!
-----------------
Step 2
-----------------
Okay so now we will be updating to radio2.22.23.02 and DangerSPL.
Reboot into recovery mode (POWER+HOME), plug your phone in via USB and toggle USB-ms and delete everything off your SD card and placethese files onto the root of your SD card. Exit USB toggle.
Scroll down to wipe data and do so.. than go to "flash .zip file" now the first file you want to flash is the radio2.22.23.02 let finish then press home+back to apply update, it should reboot back to recovery after this.
Now go to wipe again and do so.. the next file you want to flash is the G1 Spl (Hard SPL) so flash the .zip file and let finish than press home+back to apply update.
Go to wipe data 1 more time. now go to flash zip and select the "Danger SPL.zip" let finish and press home+back to apply update.
Power back on into bootloader (camera+power) and check if device says.
Dream PVT 32b ENG S-off
HBOOT 1.33.2005 (drea10000)
CPLD-4
RADIO 2.22.23.02
APR 20, 2009, 15:30:43
Click to expand...
Click to collapse
If so you can move on to the next part!
-----------------------------------------*
Step 3
-----------------------------------------
Again delete the old files off your sd card and place these files on it!!
Quick note this is the last radio update for this section, radio2.22.27.08, now if you want radio update 2.22.28.25 refer to the changing hboot section and it will have the steps to do so.
Radio 2.22.28.25 may have better reception in your area but will drain your battery quicker.
Boot up into recovery mode, go to flash zip from sd and select Ohsaka superwipe. wait till finish then go to power down!! now boot back up into recovery again.
Now do a manual wipe of data and cache.
Now flash the radio2.22.27.08 file.. let finish than flash the hboot1.33.0013d file and let it finish! then reboot the device for update to apply.
Power off the device, then reboot into bootloader (camera+power) and check if device says.
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.27.08
OCT 21,2009,22:33:27
Click to expand...
Click to collapse
*If so you now have updated both your radio and SPL and you can now flash any ROM you'd like.
But if you'd like you can follow the next step and install a custom ROM and I will show you how to partition your SD card as well.
-----------------------------------------*
Step 4
-----------------------------------------
Okay so now that you have completed step 3 you can flash a custom rom but now we must partition the SDcard.
Reboot into recovery mode and go to Partition SDcard
Partition SD. Press home.
Now I have 4GB micro SD hc. My partition settings are*
Swap: 128mb (swap is not needed and is purely optional)
Ext: 576mb ( or whichever option is closest to that I can't remember, this is for apps2ext so you can save your apps to your sd card)
Rest: FAT32 (this will once again delete everything but you should have all your backed up data on your pc)
This is what I have for my partitionings and it's works fine for me and it should for you too!
Once that is done go to SD:ext2 to ext3 and once that is done upgrade the ext3 to ext4. You now have a partitioned SD card with EXT4!!
Now all that is needed is to flash the custom ROM. I am currently running this ROM.
Now return to toggle USB-ms and place the ROM zip file from the link above as well with Ohsaka superwipe from the previous step (download it once again)
Go to flash zip file and flash Ohsaka superwipe.
Power down. Reboot into recovery.
Now return to flash zip file and flash the ROM which should be named FroyoCreamSandwhich. Once it is done it will prompt you to press HOME+BACK do so.
Now reboot your phone normally and allow it to boot up (it may take a bit the first time but this is normal when you flash a new ROM). You will now be given the option to sign in create an new account or skip (although I believe it has the option to connect to wifi built in). You now have flashed your New ROM!!!!
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
3: Changing HBOOT version
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
This option is for which ever reason you need the flash recovery/radio/etc you need the Engineer SPL. which is the SPL from step 2 in rooting. although since if you are already rooted and have the latest HBOOT then that route is not the way to go.
So in order to go back to that engineer SPL all you need to do is flash Engineering SPL zip in recovery.
Then you can proceed to update radio/ recovery etc and then flash back to the latest HBOOT which is 0013d so just download
Hboot0013dand flash it through fastboot with this command: fastboot flash hboot hboot.img
--------------------------------
No Recovery?
--------------------------------
Download: http://d-h.st/v9b2erpqfyd7/orange-1.58.73.2.nbh
Like always place the file in the same folder as the fast boot directory.
Enter fastboot and run "fastboot flash nbh orange-1.58.73.2.nbh"
Wait for it complete the flash
Boot into boot loader again and you will have an engineer SPL 1.42.2000
Now you can flash any hboot/recovery/radio via fastboot.
--------------------------------
Unroot
--------------------------------
ldrifta said:
---------------------------------------------------------------------------------------------------------------------------------------------
5~Un-Rooting
---------------------------------------------------------------------------------------------------------------------------------------------
Download these files...
DREAIMG.nbh
update.zip
Now would be a good time to un partition your sd card since there will no longer be a custom recovery..
1. first you take the "DREAIMG.nbh" file and the first "update.zip" file and place on root of sdcard!
2. start phone in recovery mode (home+power) do a quick wipe of everything! than flash the update.zip file.. wait for finish than reboot or power off.. whatever prompts tell you. than make sure device is powered off after finished installing!
3. power on via fastboot (camera+power) and wait for selection to pop up asking to install the update! press confirmation button to apply and let it work its magic!!
Now your phone will be on stock android 1.0 firmware! you have 2 options..
a. wait for automated updates.. could take up to 48 hrs..
b. flash updates to 1.5 and or 1.6 via stock recovery!
if you chose option b than you are smart! lol who wants to wait for updates for a G1 nowadays? lol
ok so now to apply updates via stock recovery you do what you would normally do.
Download these files...
Stock 1.5 (OTA)
Stock 1.6 (OTA)
(the stock 1.5 and 1.6 files are also "update.zip" so be sure not to mix them up and confuse the proccess!!)
1. Place files on root of sd.. DO NOT RENAME FILES, the stock recovery will only flash an "update.zip" so please dont make any changes to file.names...
2. boot into recovery mode (home+power) and wait for screen with yellow triangle and this thing ! now press alt+L together untill you see more words pop up on screen..
3. Now press alt+w to wipe the data on phone... (just do it dont ask why) lol after wipe is complete press alt+s to apply update! once it's finished reboot your device and you are ready to go!!
unfortunately the 1.6 i provided is not the DMD40, you still have to wait for that automatic update lol i have the 1.6 before the update... it is the official tmobile firmware its just not the latest.. never really bothered to search for latest one..
Click to expand...
Click to collapse
if any of those links are down post a reply and i will get a mirror up as soon as possible!
Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:
Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.
Your welcome guys. I ran up with some problems and my pc isn't available so ill try finishing this soon (probably in my iPod).
Okay yes this is perfect I can generate the links via the Dropbox app so hopefully this should be done soon!
Wow phew that took longer than expected (about 3 hours) safari is a horrible browser. Kept on crashing. Finally did all of it on notes and just pasted it on, revised and posted I hope this helps out! I will have the next steps up soon but for now you should be able to root your htc g1 with no problems what so ever have fun rooting guys. :laugh: I'm heading off to sleep. I'm exhausted. Later.:silly:
HTCDreamOn said:
Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:
Click to expand...
Click to collapse
Thanks!
I decided to finish up the rooting part since there was activity on the topic. Feel free to look over it just in case I may have missed something. I doubt it but hey we're not all perfect. Exhausted but pretty satisfied on how things are coming out. Mainly I'm happy to see that this is on the G1 oracle and that this this is recognized as a contribution to the g1 forums!
luggag3 said:
Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.
Click to expand...
Click to collapse
The rest is up for rooting! Have fun rooting!
Can anyone repost the file from part 1? It doesnt work...
Good work, thread stickied.
Thank you,
mf2112
XDA Moderator
duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Which one?
duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Sorry for the incovienience but since majority of this post was made on my iPod using notes since safari is higly unreliable with desktop version sites. This the format of notes is kept when copying to the post editor. Thus this is how the link was copied:
https://www.dropbox.com/s/y3slprukiqrt9nv/
EXAMPLE.DOC
Click to expand...
Click to collapse
Instead of like this:
https://www.dropbox.com/s/y3slprukiqrt9nv/EXAMPLE.DOC
Click to expand...
Click to collapse
Thus making it believe that there is a "RETURN" in the link giving you a 404 error. I fixed this along with some other 404 error links but it is all fixed. Either way next time there is a link that is not working quote it and I'll have it back up.
So I am no longer using my G1 but I will still finish this guide. I'm sorry for the wait guys.
Sent from my Nexus 4 using xda app-developers app
Nice guide.. you left 'adb shell' in the bypass google section
Thnxxx
Related
1/27/11 Update: Some members have commented that the MoDaCo Superboot method is easier, and although I haven't used it myself, it does look easier. If you want to go that route instead, you'll still need to unlock your bootloader, which means completing Steps 1-5 below. After that, you can go with the method given here: http://forum.xda-developers.com/showthread.php?t=927838
________________________________________________________
The following directions should let you root your Nexus S using an Intel Mac running OS 10.5 or 10.6. Thanks to Koush for providing the method and the recovery img, to ChainsDD for providing Superuser, and to Luxferro for providing a workaround for 2.3.1.
You should apply the 2.3.1 OTA update before obtaining root. Otherwise you'll have to do it over again after the update. If you installed a rooted/insecure boot image with the original instructions and now find yourself unable to upgrade to 2.3.1 (Status 7 error), one option is to use ROM Manager to restore the 2.3.1 Nandroid backup kindly provided by momohammed20 in this thread. From there, you will have stock 2.3.1 and can follow the steps below to obtain root again.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download the "androidsdk.zip" file from here: http://www.box.net/shared/ljhg8t5sjh
Unzip that file (if not already unzipped automatically upon download), and place the "androidsdk" folder on your Desktop. It has to be in this location for the rest of the steps to work.
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
Hit "Return" again and wait for recovery to flash.
7) At this point you should still be in Bootloader/Fastboot mode. DO NOT REBOOT YOUR PHONE*. Press the "Volume Down" key until "RECOVERY" is highlighted, and press the "Power" key to select this option.
*Note: You must go to Recovery directly from Bootloader/Fastboot mode after Step 6 without rebooting your phone in between, or else your phone will replace ClockworkMod Recovery, hang at the "Google" splash screen requiring a battery pull, and you'll need to start again from Step 6.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Look inside the "androidsdk" folder on your Desktop for a file called "su2361ef.zip", and using the Finder on your Mac, copy that file (without unzipping it) to the main directory of your mounted phone ("NO NAME").
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su2361ef.zip"
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
---------------------------------------------
To re-lock your bootloader (Optional step):
1) With your phone connected and "USB Debugging" still enabled (which it will be unless you disabled it after the above), copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
2) Copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem lock
Hit "Return".
Reboot your phone.
---------------------------------------------
Major thanks to Koush, ChainsDD, momohammed20, and Luxferro!
Your gonna need the recompiled fastboot. Then it makes it super easy.
So whats the advantage of having a rooted/insecure boot image as opposed to not? Sorry for the noob question
thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced
You freaking rock man! Thanks for this. Ill be rooting mine very soon.
I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks
Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.
rashad1 said:
thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced
Click to expand...
Click to collapse
Glad it was helpful. You should have gotten a warning on your phone screen about losing the data in Step 10, and you could have turned back at that point. I've now edited the post above to make it clear there as well.
WilliamStern said:
I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks
Click to expand...
Click to collapse
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 21.
WilliamStern said:
Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.
Click to expand...
Click to collapse
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.
Amin Sabet said:
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 20.
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.
Click to expand...
Click to collapse
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol
WilliamStern said:
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol
Click to expand...
Click to collapse
You did not flash the clockworkmod recovery correctly. The Triangle with exclamation point is the stock recovery image.
Redo the step that says fastboot flash recovery etc..etc..
Sent from my Nexus S
How about a noob guide for windows also Not that I wont be able to figure out from other sources when I want to root for the first time. But a noob guide here will come handy as well ;-)
Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?
WilliamStern said:
Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?
Click to expand...
Click to collapse
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.
jroid said:
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.
Click to expand...
Click to collapse
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.
WilliamStern said:
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.
Click to expand...
Click to collapse
What happens if you plug your phone into the USB and type adb devices?
Michael.B. said:
What happens if you plug your phone into the USB and type adb devices?
Click to expand...
Click to collapse
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found
WilliamStern said:
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found
Click to expand...
Click to collapse
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?
Michael.B. said:
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?
Click to expand...
Click to collapse
Yeah, I did the updates.
I'm gonna try again from scratch. Thanks for the help.
William, what happens when you plug your phone into the Mac, open Terminal, and copy/paste the following command (don't forget to change "Amin" to the name of YOUR home directory):
Code:
/Users/Amin/Desktop/androidsdk/platform-tools/adb devices
Typing just "adb devices" won't work because we never set the path to adb, but the above code should work (and give you a list of connected devices, which would be just your Nexus represented as a number) if you correctly did Steps 1-4 above.
Install Drivers:
Download required files HERE
1: Plug in Aria with supplied data cable to install standard drivers
2: Install HTC Sync (we only need this to get appropriate .adb drivers)
3: Install H Boot Driver - Detailed Guide HERE
a: Power down Aria
b: Hold Volume Down button and press Power (this brings you to bootloader)
c: Wait for SD Card diagnostic (about twenty seconds)
d: Plug in Data cable - at this point Windows will say driver didnt install properly
e: Navigate to Device Manager and update driver for Android 1.0
f: Select "Browse Computer for Driver" and open "Android USB Driver" folder and click next
You now have all the Necessary drivers for your new Android!!
Rooting Your Phone
Credit goes to all the great devs at XDA Developers, including Attn1 and shad0wf0x for their great work
With all the Drivers installed you can now Root the phone!!
1: Go into Menu/Settings/Applications/Development and check the box for "USB Debugging"
2: Plug in phone and choose Charge Only, check box for "Dont ask again" and DONE
3: Download and Run unrEVOked Recovery Tool as Administrator(Windows users)
(as per unrEVOked instructions uninstall any s/w that communicates with the phone(ie: HTC Sync, Doubletwist, etc.)
---Follow any on-screen instructions
**It may take a few tries(unrEVOked hates Windows)
**if all else fails, try shad0wf0xs' Ubuntu Live CD method HERE
Congrats!! you have Rooted your phone
Un-Rooting(Restore to factory)
All drivers from above must be installed
1: Official ATT 2.2 Update(NOW Rootable!!! Click ME) or ATT 2.1 Update Download
2: Make sure USB Debugging is checked in Applications/Development(if fail, then uncheck debugging)
3: Run Aria Shipping ROM.exe as Administrator
---Follow on screen instructions, may take up to ten minutes
Install Custom ROM's
Once youre Rooted you can install custom ROM's from Clockwork Recovery;
1: Copy a custom ROM to the SD card
2: Power down phone
3: Hold Volume down key and press Power to enter bootloader mode
4: After diagnostics run, choose "Recovery" from the list and press power button to select it
5: In Recovery menu choose "install zip from SD card"
6: now select "Choose zip from SD card"
7: navigate to the custom ROM and install
**NOTE: Before flashing a custom ROM it is highly recommended you Wipe Data/Factory Reset in Recovery first
it is also good practice to make a Nandroid backup before flashing any custom ROM
Install Custom Font
Credit goes to churapa. Nice work Bro!! Original Guide HERE
**ROOT Is Required for this
**ALWAYS make a Nandroid Backup before attempting any Mods
-Things you will need:
-True Type Fonts(both Normal and Bold .ttf)
-ADB Tool and knowlege of use
-Required Drivers for proper communication between PC and Android
1: Copy both fonts (normal and bold) into folder named Androidfonts
2: Rename fonts to DroidSans and DroidSans-Bold
3: With the phone off Enter Recovery mode by holding Volume Down key and press Power, select Recovery from the list
4: Once in Clockwork Recovery choose "Partitions" and select "mount system"
5: Connect Phone using Data Cable and run ADB Tools in CMD (c:\Android\Tools)
6: now in CMD window enter the following command:
adb push c:\androidfonts\DroidSans.ttf /system/fonts/DroidSans.ttf ENTER
adb push c:\androidfonts\DroidSans-Bold.ttf /system/fonts/DroidSans-Bold.ttf ENTER
7: Now exit CMD, unmount phone in Partitions menu, Go Back, Reboot Phone, Disconnect USB cable
Enjoy your new font!!
NOTE: Respectively you can backup your current fonts by entering the following in ADB:
adb pull /system/fonts/DroidSans.ttf c:\androidfonts\backup
adb pull /system/fonts/DroidSans-Bold.ttf c:\androidfonts\backup
How to Sideload 3rd Party Apps:
(Rooting NOT required for this)
Download SDK Tool HERE
1: Un-RAR Android folder to root directory on PC (ie: C:\ )
2: Open CMD Prompt and type CD\ and hit Enter
3: Now type cd\android\tools Enter
4: Plug in Data cable and choose "Charge Only" on phone (always choose this)
5: Now in CMD prompt enter this command: adb install barcodescanner3.4.apk and press Enter
The SDK tool should install the Barcode Scanner app on the phone. Yay!! Success!!
**You can use this method to install .apk downloads onto the phone. For this demo i had already inserted
the Barcode Scanner app into SDK tools folder. the actual command should read as follows:
adb install c:\path to .apk file (ie: adb install c:\apps\filename.apk)
**I chose this app because you can use it to install other apps by scanning the barcode
found on many HTC App sites.
How to apply ringtones over 300kb limit:
Short story first
I wanted a nice free app to manage files, so i installed Astro File Manager using Barcode app from above.
While moving some files around i discovered the option to set mp3's to ringtone... and it worked!!
This is good because i was not happy to see there was a 300kb limit to ringtones. There may be another
or better way, but this is how i did it
1: Go to Astro app website HERE
2: Scan the Barcode with Barcode scanner app to install Astro Direct link HERE
3: Open Astro, navigate to SD Card\Mobile\Music
4: find the music file you want set to ringtone, Hold on it until menu pops up
5: Select "Music Options", select "Apply as Ringtone"
or if you dont wanna go through all that hassle, install Rings Extended App. Direct Download HERE
How to remove unwanted Stock Apps using SDK:
1: Once your phone has been rooted with Clockwork, boot into Recovery(hold volume down/press power)
2: Open CMD prompt, get to the "android\tools" directory
3: In recovery window highlight "Mount System"
4: Plug in data cable, in CMD type adb remount
5: Now enter adb shell
*you can view the list of apps stored in the phone by entering ls
6: To remove an app enter the following: rm whateverapp.apk, then enter rm whateverapp.odex
(example: rm HtcFacebook.apk ENTER then rm HtcFacebook.odex ENTER)
7: Type ls again to confirn they have been removed, reboot phone.
*NOTE: you may get 0.0dip listed in Widgets menu. simply go into Manage Apps and locate HTC Sense. Open it and "clear data". your display settings will be reset to factory, but it gets rid of the false data.
Stay tuned!! More to come
Nice tut I could easily follow it
Sent from my Liberty using XDA App
Nice post man... way overdue. Hopefully the mods will sticky it and head off a lot of frustrated searches! =)
Nice guide man...you should sticky this and continue to add stuff to it.
works on htc gratia a6380 with hboot 1.00 ? ? ?
thanks
kiko85 said:
works on htc gratia a6380 with hboot 1.00 ? ? ?
thanks
Click to expand...
Click to collapse
Sorry, there has not been any procedure documented for rooting the Gratia with hboot 1.00. If you search this forum you will find some posts and references for things to try, but nothing concrete has been published yet.
Really good post. Very helpful
Sent from my HTC Liberty using Tapatalk
happy you guys like it. the idea is to be very simple and straight forward.
most of the info comes from XDA guides here. i hope an Admin will sticky this so it will be handy for others to use
i recommend to add the guide to Changing the default font of your Aria
http://forum.xda-developers.com/showthread.php?t=869302
Well, that was quick and easy. Thanks!
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Javi97100 said:
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
CMD = command
CMD is the command you type into run (Start - Run) to open a command prompt.
Javi97100 said:
Um Im sorda nooby at this but what is "Cmd"?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
If you are using Windows Vista or Windows 7, this is the black command window that allows you to enter commands such as "COPY", "DIR", "XCOPY", etc.
Cool can I get a link to download and install this?
Sent from my Liberty using XDA App
Oops never mind its on the first page
Sent from my Liberty using XDA App
kevina90 said:
i recommend to add the guide to Changing the default font of your Aria
http://forum.xda-developers.com/showthread.php?t=869302
Click to expand...
Click to collapse
done Bro, added a revised version to the main guide
tested it out on my Aria first, everything worked perfectly.
Hey Zed,
You might want to add to the Font section that you can change your LockScreen font using exactly the same method, but the font for the LockScreen is named Clockopia.ttf -- I'm sure anyone who changes their fonts will want that one changed too.
Also, on the pull command to back up your fonts, you need to add a \ after backup. I did it your way and it wrote the fonts into a file called backup. Then each time I entered it again to back up another font, it overwrote the previous one. Maybe the pull commands should also be moved up into the actual instructions instead of a footnote too, in case someone doesn't read all the way through before starting the process. It will be too late if they have already followed the instructions in their current form.
These are just suggestions, not criticism. Love the thread, thanks a lot for creating and updating it!
Thank you so much for this thread. It made rooting my Aria and putting on the latest liberated froyo ROM super easy. I was a root/custom rom virgin before yesterday!
I'd also add a rom list so people can stay updated.
911jason said:
Hey Zed,
You might want to add to the Font section that you can change your LockScreen font using exactly the same method, but the font for the LockScreen is named Clockopia.ttf -- I'm sure anyone who changes their fonts will want that one changed too.
Also, on the pull command to back up your fonts, you need to add a \ after backup. I did it your way and it wrote the fonts into a file called backup. Then each time I entered it again to back up another font, it overwrote the previous one. Maybe the pull commands should also be moved up into the actual instructions instead of a footnote too, in case someone doesn't read all the way through before starting the process. It will be too late if they have already followed the instructions in their current form.
These are just suggestions, not criticism. Love the thread, thanks a lot for creating and updating it!
Click to expand...
Click to collapse
all suggestions are appeciated. good thoughts bro, soon as i have time it will be done
***
If you're looking for a guide on how to root on Windows, there is a fantastic guide here written by W0lv3r1n3!!
***
I know there is a stickied guide for this but it hasn't been updated since 2.3.1 so I decided to update it a little bit just to make things easier for people. Credit for this goes to Amin Sabet and DistortedLoop with a few changes/additions by me.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download this file (http://dl.dropbox.com/u/22368847/adb-fastboot.zip) and unzip it to your desktop (Inside you'll find all the files you need to proceed including "adb", "fastboot", "recovery-clockwork-3.0.0.5-crespo.img", and "su-2.3.6.1-ef-signed.zip").
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery-clockwork-3.0.0.5-crespo.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Some people with new Nexus S' are finding that the file discussed in the following steps does not exist. If you cannot find it but can still reboot into Clock Work Recovery Mod then don't worry, you're still rooted and fine!
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
~~~~~~~~~~~~~~~~~~~~~
Updated for ICS and included instructions in the zip!
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
Mods any chance we can get this stickied to replace the old one? There seems to be some confusion about using the old version to root.
Nicely done.
any guides to root 2.3.3 for windows?
J__ said:
any guides to root 2.3.3 for windows?
Click to expand...
Click to collapse
Honestly, its a very similar process. Just download a different version of the SDK and make sure you put the recovery image in the folder of the installed SDK called tools. Then when you get to executing the commands do this:
Code:
cd *remove the asterisks and type the file path to the directory for the tools folder of your SDK folder in program files*
Then remove the
Code:
desktop/adb-fastboot/
and just type the other parts.
jlevy73 said:
Nicely done.
Click to expand...
Click to collapse
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
im getting this error message "cannot load 'recovery-clockwork-3.0.0.5-crespo.img'"
so stuck on step 6. any advice?
thanks
Also, curious because now I have an unlocked bootloader but nothing else has been done. This shouldn't be an issue I assume.....
I've never heard of someone having that issue. Try the command fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img
Sent from my MattedBlues CM7 Google Nexus S!
kenvan19 said:
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
Click to expand...
Click to collapse
I don't think it's enough but it would make a great add-on to the original rooting for mac thread.
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
owlmatt said:
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
Click to expand...
Click to collapse
Did you install the android SDK? I'm a little lost, I'm not sure what could be going wrong...I used this method to root both my and my wife's phones with no issues.
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
owlmatt said:
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
Click to expand...
Click to collapse
Oh no! I see where I screwed up in my guide...I'm sorry I see it clearly now...don't know how I missed it before.
instead of
Code:
~/Desktop/androidsdk/tools/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
type
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
owlmatt said:
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
Click to expand...
Click to collapse
Okay I have one last idea...I'll grab the link then edit this with the stuff...brb
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.
I AM ROOTED!!! How do I buy you a beer?
owlmatt said:
I AM ROOTED!!! How do I buy you a beer?
Click to expand...
Click to collapse
Haha don't worry about it man! Just glad you're rooted now
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
owlmatt said:
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
Click to expand...
Click to collapse
If you really want to do something, I'd suggest buying the XDA Premium app from the market and help support XDA as a whole.
Consider it done.
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
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.