Database Users

[GUIDE] MAC Rooting Nexus S

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.

From stock 4.5.141 to CM7.2RC2 (a brief how-to)

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?

*UPDATED**UNLOCK TOOL (4-2019) for ALL Versions of BLU R1-HD

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.

Fool-proof, 100% squeaky clean oneplus 2 custom rom installation for max stability

​Welcome to a simple tutorial that will help OnePlus 2 (OP2) owners and possibly other device owners install custom ROMs in such a way that eliminates most, if not all possibility of system errors, resulting in the longest lasting and most stable custom ROM installations!
DISCLAIMER: Your Warranty was voided long before you were ever even ready to complete this tutorial.
Therefore, I am not responsible for a broken or bricked device, especially if your rage towards a bricked device caused you to throw your device into a wall. This tutorial is actually designed to reduce the amount of "Rage Quitting" on modifying your device.​
This Tutorial assumes you have already completed OEM Unlock, Root, installed TWRP or other Custom Recovery, and are basically ready to install a custom ROM on your OP2.
Before beginning, backup any files you may need, I upload mine to my Google Drive then download after completing the ROM install. You can also use Nandroid to backup your current system (optional as there are methods to restore even the most bricked OP2 that doesnt even have a working recovery or OS, trust me I have done it at least 5 times because I constantly try new ROMs and mods). There are three necessary prerequisite steps required to complete before using this method to install your custom ROM. These prerequisites are listed below:​
Prerequisite One: Ensure your OnePlus 2 has been FULLY updated on the stock Oxygen OS ROM before you install your TWRP or other Custom Recovery. If not, Return to factory ROM, Un-Root, and update until you cannot update any more, then return to this tutorial afterwards.
Prerequisite Two: Ensure your OnePlus 2 has the latest update of the TWRP or other Custom Recovery. The Latest TWRP for the OP2 can be found here: https://twrp.me/oneplus/oneplustwo.html
Prerequisite Three: Ensure your device can receive files via ADB PUSH while in custom recovery. To do this, reboot your phone into recovery, connect to PC, hold down the "Shift" key and while holding, right-click in a window containing a file you wish to transfer, and select "Open Windows PowerShell Here" or "Open Command Prompt Here". Use the command "adb push Lin15.zip /sdcard" (remove the quotes, "Lin15.zip" is an example file) to push the file onto your device. Then, if your custom recovery has a file explorer as TWRP does, use it to navigate to /sdcard and see if the file is there. Also, your windows should show a successful transfer and should say "Okay" underneath your command line. If unsuccessful, install OnePlus 2 Drivers along with Universal ADB drivers and then try again. If still unsuccessful, try TWRP 3.1.1-0 (Download Link Below 2 Paragraphs in Blue Text Section). If unsuccessful at this point, there is something wrong as Win 10 with OP2 Drivers, Universal ADB Drivers, and TWRP 3.1.1-0 is my exact setup.
There are many custom ROMs available for the OP2. The method for installing custom ROMs is generally the same, but can differ in certain ways. This method SHOULD work for your custom ROM, but is not guaranteed. If this method fails, then visit your custom ROM's development page, and follow their instructions instead.
In this Example, I will be installing the latest (at the time of writing) Lineage 15 Android Oreo 8.0 Third Alpha Build OS/ROM and will be including instructions for the proper installation of the A.R.I.S.E. Magnum Opus System Sound Mod (Based on Viper4Android). I will include links to downloads, but their main XDA page can be found here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 This installation will use the latest (at the time of writing) TWRP 3.1.1-0 Custom Recovery.
INSTALL TIME:​
Begin by rebooting into recovery. Under "Wipe" options, you will first want to format data, select the option and type "yes" when prompted to confirm the operation. Repeat this step once again to ensure a squeaky clean wipe.
Next, also under "Wipe" Options, select the "Advanced Wipe" Options. You will then select EVERY BOX (Yes, this includes Internal Storage and will wipe EVERY SINGLE FILE from your device, this is INTENTIONAL and is why you MUST have a device that can accept ADB PUSH files in recovery!). This will wipe every file from existence, completely. This is what allows such a stable, squeaky clean install, as not a single piece of evidence from any other ROM/OS will be left behind, leaving basically no chance for errors or conflicts during installation of new ROM. You will want to complete this step again to ensure a squeaky clean wipe.
Navigate to the TWRP Home/Start-Up Screen and connect your device to your PC (WARNING: DO NOT USE ADB SIDELOAD MODE!!! I HAVE NEVER, EVER HAD A SUCCESSFUL ROM INSTALL FROM SIDELOAD!!!). Simply leave the device at this screen, and do not touch it. At this point, if you do not have all the necessary files to install your custom ROM and mods, you will need to download them now. I ALWAYS recommend the "Pico" Gapps package if installed in a ROM (some ROMs include Gapps). The reason for this is because the Pico package includes the bare minimum to get Google Play Services and Google Play Store up and running. This eliminates unwanted Gapps and reduces the chance of installation conflicts. The golden rule is: The less you install in TWRP, the better. If you want more Gapps, then after setting up the phone at the end of the ROM install, just search for them in the Google Play Store, its how I get mine every time. In the case of Lineage 15, the list of downloads is below:
Lineage 15 OS/ROM: https://www.androidfilehost.com/?fid=961840155545594199 (Dev Page: https://forum.xda-developers.com/oneplus-2/development/rom-lineageos-15-0-t3668056)
Android Oreo 8.0 Pico Gapps Package: https://www.androidfilehost.com/?fid=817550096634796662
Super SU 2.82 Root Installer (Select the Flashable 2.82 ZIP file): http://www.supersu.com/download
BusyBox Flashable Zip Package (Large page with many tools, scroll down to find the BusyBox tool): https://forum.xda-developers.com/showthread.php?t=2239421
A.R.I.S.E. Magnum Opus System Sound Mod (Select the "ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip" Option): https://www.androidfilehost.com/?w=files&flid=176171
Once all necessary files are downloaded, give them their own folder inside Windows and rename all of them to something simple as shown here:
View attachment 4273530
(Lin15.zip, Gap.zip, SU.zip, Busy.zip, Arise.zip)
Ensure your device is in custom recovery at the home/startup screen and is plugged firmly into your PC. DO NOT navigate ANYWHERE inside custom recovery or touch the device.
Now we will ADB PUSH these fresh install ZIP files over to your device. Inside the window containing your downloaded ROM files, hold down the "Shift" key and while holding, right-click and select "Open Windows PowerShell Here" or "Open Command Prompt Here". To ADB PUSH files, simply type "adb push FILE.zip /sdcard" where "FILE" is the target file and "/sdcard" is the target destination. Correct capitalization of letters is IMPORTANT! My window looked like this when finished:
View attachment 4273532
(adb push Lin15.zip /sdcard, adb push Gap.zip /sdcard, adb push SU.zip /sdcard, adb push Busy.zip /sdcard, adb push Arise.zip /sdcard)
Your ROM files should now appear on your device at your target destination. Disconnect your device and use the Custom Recovery File Explorer to navigate to the destination to confirm. "/sdcard" is the easiest to use destination.
Now we will install ALL of the ROM files, back-to-back with NO REBOOTS, NO WIPES, NO OPERATIONS WHATSOEVER INBETWEEN INSTALLS, THIS IS EXTREMELY IMPORTANT!!! Navigate to the Custom Recovery "Install" Section and navigate to your destination for your files. Flash the ZIP files in this order EXACTLY: Lin15, Gap, SU, Busy, Arise.
The A.R.I.S.E. Instillation is an AROMA style installer. It is a HUGE Sound Mod suite containing many options. Select the sound mods you like, but there is a module that is REQUIRED and 4 others that are highly recommended, listed below:
CORE Module is REQUIRED!!! Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions fix are all highly recommended no matter what the ROM or mods, just in case. If these problems do not exist, selecting the options will not change anything, so do not worry.
My personal A.R.I.S.E. install included the following modules and delivers absolutely AMAZING sound quality while keeping installed modules to a minimum (otherwise known as a "Lightweight" install): Core Module, Viper4Arise 2.5.0.5, Viper4Arise Profiles, Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions Fix. Its a highly recommended package
ONLY AFTER ALL FILES HAVE BEEN INSTALLED, navigate to Custom Recovery "Wipe" section, select "Advanced Wipe" and then check the "Dalvik Cache" and "Cache" options, DO NOT SELECT ANYTHING ELSE OR YOU WILL NEED TO START COMPLETELY OVER, WIPE PHONE AND RE-ADB PUSH FILES TO ENSURE A SQUEAKY CLEAN INSTALL!!! Perform this step again to ensure a squeaky clean wipe.
YOU ARE NOW FINISHED WITH A SQUEAKY CLEAN ROM INSTALL BUT THERE ARE A FEW MORE RECOMMENDED STEPS!
Recommended: DO NOT immediately reboot into system after install. Instead, navigate to Custom Recovery "Reboot" Section and select "Power Off" Instead. Once device is off, plug into A/C Outlet charger (DO NOT USE A PC, DETECTION OF PC WILL CAUSE DEVICE TO BOOT), and allow to fully charge, then cool off. This will ensure that Battery Calibration is set to 100% upon Initial Boot
Initial Boot: Boot Device, Initial boot will take around 5-10 minutes. DO NOT TOUCH THE DEVICE DURING THIS TIME. When you see the startup screen, STILL DO NOT TOUCH THE DEVICE! Instead, allow device to sit and idle, allowing the ROM to "Settle" for a MINUMUM of 5 minutes, 10 is recommended. Then, BEFORE setting up the device, reboot and allow another 5 minutes of "settling".
Run through the Device Initial Setup. You will want to select any desired options now, and avoid having to search settings later. Once at Device Home Screen, immediately open app drawer and select SuperSU app. Inside SuperSU, navigate to settings and apply the following options:
Disable Re-Authentication, Default Access: Grant, Enable SU During Boot, Trust System User
These SuperSU options will allow mods to function with complete stability and no interference, leading to a smoother experience. After, completing this step, Reboot your phone and ENJOY YOUR NEW, ROCK-SOLID, STABLE ROM INSTALL!!!

Nice job bro thanks working here!

Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?

Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.

shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Now I tried it again and this time flashed busy box as well but the same error.
Screen shot for your reference. Is there another way to install it?

shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.

pops106 said:
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
Click to expand...
Click to collapse
Well we all know performing this method of install is not a requirement for installing ROMs, but it is the most fool-proof method and ensures there are no file conflicts between old and new ROMs/OS's. I cannot even tell you how many times I have done quick, minimal work installs and end up with tons of errors, laggy or freezing screens at random times, force closing apps, busybox system link failures, the list goes on and on. After using the "Squeaky Clean" method, I can honestly say Lineage 15 is as stable as the Stock/Factory Oxygen OS.

wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Thanks. I got it install using a different method and it is working wonderfully.

wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Fair enough
And thanks to the opp for the thread

pops106 said:
Fair enough
And thanks to the opp for the thread
Click to expand...
Click to collapse
No problem, the thread was a random idea after accidentally stumbling across the fact that TWRP can accept ADB PUSH files. I honestly had no idea, and was stuck in a bootloop after a custom ROM failed to install correctly. I had no backup and was getting ready to just give up, enter Qualcomm Diagnostics Mode and perform the Oxygen OS Firmware/Software OEM install when I decided to reboot into Recovery and attempt SideLoad of a previous ROM that had worked.
This did not work, as sideload is apparently a dumb way of doing things. I never understood why sideload tries to install a file that is in the middle of transferring. Just seems like a flawed concept to me. Anyways the install was very slow, buggy and laggy, and when finished had installed such a corrupt system, due to installing a partially transferred file while it is being transfered and then sticking all the pieces together, was so unstable that more than a minute idling at the home screen or any attempt to open ANY app caused the phone to reboot.
Sideload is a worthless feature in my opinion and I will never use it for any operation ever again so long as I live. So all of a sudden I decide to plug the phone into my PC while in recovery and observe how Windows detects the phone when you turn Sideload mode on and off, as to try and troubleshoot my sideload to get an effective install (which by the way will never happen, to this day I have never had a sideload install work correctly), and noticed when I turned it off, the device still showed up as a recognized Android device under Windows Device Manager. Then, you may not believe me on this, but I did actually randomly decide that more than likely, it was interfaced on Universal ADB, and that it I typed "adb devices" into a windows command prompt, it should show, and it did. The rest is history.
I know the feature had been around for some time as I found out later on, but I had never seen any information about it anywhere on any thread, and even when I asked for ideas for troubleshooting, while XDA users helped for sure, I guess they just didnt have that idea, and gave me alternative routes as well such as the Qualcomm Diagnostics full OEM wipe method which I was already familiar with. This does show, however; that experimenting and troubleshooting on your own can be a great way to learn new things!

Hi, thank you for the post.
I am enjoying v4a bcoz of you only.
I got a query btw, can I install dolby & atmos along with v4Arise?

Please add a note for HaruhiOS
HaruhiOS checks if a clean flash is required before flashing and will abort to tell the user that a clean flash is necessary if ever. It is my design goal to avoid the need for clean flashing as much as possible
Due to this the user should avoid unnecessary clean flashing, which actually ruins performance and battery life and reduces device health when using my ROM

if already.....
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.

magnamentis said:
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
Click to expand...
Click to collapse
Apparently e2fsck and fsck.f2fs is too hard
Once the storage card is corrupt no formatting will help you anyways
Just stop believing in dumb stuff. If you have to clean flash every other build a ROM developer releases they messed up big time and they should fix their code

COMPLETE GUIDE: Installing Android 11 with GApps and Rooted System with Magisk on Razer Phone 2

Update: At the time of writing this, I completely forgot that I am running Linux Mint - Cinnamon 20.1 on my laptop, which connects the bluetooth with my phone just fine. However, it did NOT work when I booted into windows and tried it. I am not sure why this is, but just beware. I recommend that you look into it yourself and see if you can find a resolution that works for you if you aren't using a linux os.
Hi everyone, after using another guide on here by Marcos8760, I noticed that there were a lot of things missing from the steps layed out, and decided to create my own guide with every step that should be done to have a fully functional Razer 2 with Android 11 OS. I will be using a part of his guide in this tutorial, and the link to his if you want to check it out is: https://forum.xda-developers.com/t/guide-android-11-gsi-with-gapps-and-root-magisk.4216117/
**DISCLAIMER**
First, I am not responsible for any bricked devices or errors that occur. This is completely at your own risk.
Second, this OS is NOT supported by Verizon. If you use Verizon then this will not be able to work on your phone.
Third, MAKE SURE that you have backed up all your files and data before doing this, again, I am not responsible
for you losing your data, because you will lose it if it isn't backed up, and I have warned you to do so.
Fourth, any commands will be in '' quotes, do not type these into your own cmd window, they are just to indicate what the commands are.
Last, This is not a troubleshooting guide, I am not covering how to fix errors, only simply how to install and get working with the Android 11 GSI. If there are errors please try to do research and resolve them on your own.
Before we begin anything, we need a few tools. These are the download links to all the files you will need to complete this process.
1. You will need a program such as WinRar, 7zip, or my personal fav, WinZip, to be able to extract these files, make sure you have one of these installed before proceeding.
2. We need to have a backup of the stock firmware in case of any kind of bootlooping or other bricking that might occur that you can revert back to. Extract this.
Link: https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3201-user-full.zip
3. This is the link to the GSI we will be installing. If you want a rooted system, you need to download system-roar-arm64-ab-vndklite-gapps.img.xz file. This will allow you to install Magisk and enable Google's Play Protect which is what this guide will be about, of course you can choose your own, however you will have to figure out how to get play protect certified yourself. Extract This.
https://github.com/phhusson/treble_experimentations/releases
4. We need the kernel that allows TWRP to be installed, which is the file manager we will be using for some of the programs we need to install, as well as being able to boot the phone up during this process. Extract This.
https://github.com/francisrosario/a...load/4.0/TrinityKernel-kernel-r4-20200512.zip
5. This is a file system program used to write large scale data with much faster read and write speeds for Linux and Android systems alike. Here is a link to learn more about it: https://c.mi.com/thread-2487060-1-0.html
*DL link: https://arter97.com/browse/aura/f2fs/20190114/f2fs_fstab.zip
*Leave this as a zip file, you just simply need to save it.
6. Here is the link to the latest Magisk version. (Needed to root the device) Leave as zip file.
https://github.com/topjohnwu/Magisk/releases/tag/v21.3
7. We need a program called VoLTE Fix-It. This is needed to enable your mobile network and data for LTE on this GSI.
*https://github.com/KhushrajRathod/VoLTE-Fix
*Just press the green 'Code' button and download as zip. Leave this as a zip file as well.
8. We need the Android ADB Driver to be able to enter commands to install everything.
https://developer.android.com/studio/run/win-usb Click download zip, accept agreement, and download and extract.
9. We need Android SDK Platform Tools to be able to run fastboot and adb commands. Extract this.
https://developer.android.com/studio/releases/platform-tools
10. Lastly, (I promise), you need the Qualcomm Android USB Driver. The link explains why. Extract this and go through the setup and install.
https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
Now we can begin the process.
First, copy all of the files in the aura-p-release folder, and paste them into the platform tools folder where all of those files are. Then enable USB debugging on your phone. Go to settings, click on About Phone, scroll to bottom and tap "Build Number' 7 times. You are now in dev mode. Search in the search bar for usb debug, tap it, then enable it and select allow.
To install the Android ADB driver, right click on start (Windows icon in bottom left of task bar), select device manager. Then we need to go into fastboot mode. Hold both volume buttons and power button down, be patient, it takes a second. When the screen goes black immediately press and hold the Volume down button for at least 3-5 seconds until a screen comes up that has an option to 'Restart Bootloader' at the top. Now we can install the driver. You should have device manager open, an option called 'Other devices' should come up, with Android that has a yellow exclamation mark by it. If it doesn't, unplug and replug the phone's usb, and it should. Once that shows up, right click and select update driver. Select Browse computer, select Let me pick. Show All devices should be selected, if not, go ahead and do so, then click next. Select 'Have Disk', Select Android ADB Interface, click browse and go to the folder where you downloaded the ADB driver, then select 'android_winusb' and click ok. Click ok again, a warning will come up, you don't need to worry it is needed to install this OS, so go ahead and click yes. It should install, you can close out when it is finished.
Next, in file explorer open the folder with all of the platform tools and aura-p-release files. Erase what is in the address bar, and type 'cmd', press enter. This will open a command prompt window in this location. Now, type in the cmd window, 'fastboot devices' and a serial number should show up. If not, then you have done something wrong or missed a step and need to uninstall the driver and go back into fastboot mode and do it again, or refer to the last disclaimer I made. Now, if the serial number did show, we can proceed. First we need to unlock the bootloader (if it isn't already) to be able to root and install. Type in the cmd window 'fastboot flashing unlock' and press enter, a confirmation should pop up on the device, use the volume buttons to navigate and the power button to select and confirm. When thats done, type in 'fastboot flashing unlock_critical', again a confirmation should come up so just do the same.
We can get into the meat of the installation process now.
You should still be in fastboot mode. In the cmd window, type 'fastboot flash system' and drag and drop the system-roar file you downloaded and extracted in file explorer into the cmd window.
Your command will look a little something like this: fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
The file path will be different depending on where you downloaded the image to.
Wait until it says complete or something similar like done and has no errors. Then, its time to flash the kernel. Navigate to the where you downloaded the TrinityKernel file, open it. There should be a .img filed simply called 'boot.img'. Go back to your cmd window, and we will be typing in: "fastboot flash boot" then drag and drop the boot.img file, like you did with the system file, again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select restartt bootloader with your power button on your phone. When it reboots, go to recovery mode, check never show this screen, and swipe where it says to swipe. Go to the wipe menu and then tap on format data. Type yes and then press enter/ok. Go back to your computer and open file explorer.
Next, copy and paste the f2fs zip file using windows explorer into the Razer 2's internal storage.
Head back to your phone, and press install. Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that go back to the TWRP home screen, button that looks like a house at the bottom in the middle, go to the reboot menu, then reboot into recovery. When it reboots, go to wipe menu, and tap on format data and type in "yes" and tap ok again. Click on "don't install" because you don't need the TWRP app on your phone.
Next we need to install magisk to enable google play protect cert and have a rooted system. Just do the exact same thing that you just did with the f2fs file, except do not format data this time.
Select mount and check all the boxes. Go back to home page and select install, scroll to magisk and swipe to install.
Now, this is where you have to make a big decision. Bluetooth on this rom is a fickle son of a gun. I have tried to make it work on a pc that doesn't have bluetooth software built into it for a very lengthy amount of time, trying all sorts of things. The only way I could get it to connect is by setting it as a device to control with my keyboard and mouse. Maybe you will have better luck, but I have confirmed that the bluetooth works on devices with already built in bluetooth software. It works perfectly on my laptop and in my car. So, if you want to proceed with this, then I will tell you, if not, you can skip over it.
Select advanced on the home menu, go to file manager, select vendor then overlay. delete BOTH the bluetoothcommon.apk and razeraurabluetooth.apk.
This step applies to those who skipped the bt part as well. Go back to home, select reboot and click system, when it reboots, select allow usb debugging, DO NOT DO ANYTHING ELSE. THIS IS CRITICAL. Go back to your cmd window and type "adb devices", a serial number should show, then type the following cmds in order: "adb root", "adb shell", "mount -o remount,rw /", "mv /bin/resetprop_phh /bin/phh-resetprop" - if this one gives an error saying its in use, don't worry, just do the next cmd, which is "phh-securize.sh"
If the 3rd cmd gave the error, the last cmd will ask if you want to confirm it, click y for yes for each option it gives, it should go thru and the device should reboot.
Now then, it may seem slow during set up, but set it up like normal. Everything should be well and good. after you finish setup, to enable better fps, go into settings, select phh settings, select misc features, scroll down to and click on 'force fps', select the last option to have 120fps, but you have to do it twice because for some reason it doesn't change to the very last option the first time.
Now, we have to setup your mobile network with volte, it is a program that allows LTE coverage from your carrier to enable data on custom gsi roms. Now, go to the volte fix it zip file in file explorer, copy paste to the phone's internal storage. Go into fastboot mode, select recovery, it will boot into twrp. Do the same thing as the other zip files, install then select and swipe. Now press home button and select reboot, click system. Go to phh settings, click ims features, check the boxes on the bottom 2 options, click on create ims apn, it wont do anything, then click install ims apk, when it is done a notification will pop up on the bottom that says to reboot, you may now reboot the phone. Once it is booted up, go to network and internet, select mobile network, change pref network type to lte, then enable volte. You should have full service of your mobile network.
There are a few last things. The default camera sucks, I've tested some from the play store, and YouCam is by far the best free camera you can get from there. 2nd, to enable the backlight on the Razer 2, download and install logo+ apk, grant it root perms, and you can select the effects and colors you want it to be. This should be everything to get you going on the gsi. If you want to do custom things like custom boot animations or alarm sounds or whatever, download either root browser or pay for root explorer on the play store, and you can look up how to do whatever you want and you can do it through one of those. There it is. Enjoy the new os and have fun with it!
**IF YOU DO RUN INTO A BOOTLOOP OR ANY SORT OF BRICKING, RETURN TO FASTBOOT MODE BY HOLDING POWER, AND HOLD VOL DOWN WHEN THE SCREEN TURNS BLACK. You can go into platform folder, find the flash_all.bat file, double click and it should bring the phone back to original stock, and you can start over. IF YOU HAVE ANY OTHER ERRORS DURING THIS PROCESS PLEASE TRY TO FIND THE RESOLUTION YOURSELF. This is NOT a troubleshooting guide.**

Nice guide!

The link in Step 4 is broken.

hey i am attempting to install VOLTE because my data works just fine, but i cant make any calls from my phone. I get the error `mobile network is not available` but my data not connected to wifi works. Any ideas. I followed your instructions to a T. i am also on verizon RP2 on Havoc OS if that helps
Thank you Ahead of time!